asdf-devel January 2022

asdf-devel@common-lisp.net

2 participants
4 discussions

Forever Stable Branch
by Michał "phoe" Herda 20 Jan '22

20 Jan '22

Hey, I've poured my thoughts related to recent events into a blogpost that turned into a long-ish article. This mail is purely informational; comments via mail are welcome but not required. https://gist.github.com/phoe/7d24bdb1f2be76a02fecba8cfecbef38 Linking a Reddit thread below and attaching the original article to this mail for posterity. https://www.reddit.com/r/Common_Lisp/comments/s8r075/ BR ~phoe

1 0

Quick note
by Robert Goldman 18 Jan '22

18 Jan '22

I have a crush of things going on in the next week, so -- although I regret it, because there are a number of very interesting issues to see to right now! -- I will be largely unresponsive for up to a week. Sorry about that, but it's unavoidable. Best, R

1 0

Earlier posting
by Robert Goldman 10 Jan '22

10 Jan '22

I have received some nice emails, and I appreciate them very much. However, in other fora there have been discussions about ASDF and Flexi-streams. That may be interesting, but it misses the key point -- or perhaps it reinforces the key point: this community seems to think it's normal for someone to say that they want to pressure another volunteer maintainer into changing a decision they don't like by breaking software, and trying to raise anger in the community. Surely a little attention to today's news shows that rage-stoking is not a means to building a healthy community of any sort. I understand that confronting this issue is more difficult than talking about whether or not ASDF should be issuing a warning. But that's not the question that is at hand. I will move to silence on this certainly at least for the rest of the day. Best to all

1 0

Considering resignation as maintainer
by Robert Goldman 09 Jan '22

09 Jan '22

I have discovered that Stas Bokuraev is continuing to refuse to update Edi packages to modern ASDF system-naming. This would not be bad in and of itself, because these are open source systems, and they can be forked. What *is* bad is that he has publicly stated that he is doing this hoping that the resulting warnings will break people's systems and thus cause them to get angry and complain to me about ASDF checking system names. What is even worse is that the CL community tacitly accepts this as normal behavior. I would like to see the CL open source community pause and consider what constitutes a healthy community. I don't believe that someone trying to break things in order to pressure a volunteer maintainer of infrastructure is something that a healthy community should accept. If the community prefers a more rough-and-tumble approach, I can accept that, but if so it's time for the community to find an ASDF maintainer who is more in harmony with the values it (at least implicitly) espouses.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel January 2022