On 27.05.2020 20:35, Stefan Sperling wrote: > On Wed, May 27, 2020 at 07:48:41PM +0200, Branko Čibej wrote: >> On 27.05.2020 19:30, Stefan Sperling wrote: >>> Out of the blue, I have received nitpicking of changes I made to the >>> website and the announce message I sent. I've received this feedback >>> via the mailing list moderation mechanism. >>> >>> Can anyone tell me what's going on here? Who even wrote this? >>> >>> FWIW, the announce message was generated by release.py; if there's >>> something wrong with that, we need to fix that script. >>> There's nothing I could do now to correct the announce message >>> itself since it has already been approved (by me). >> >> This moderation is completely inappropriate. Moderation is supposed to >> filter spam from the announce@ list, not pontificate about the names of >> the files in a release. That's what dev@ is for. You don't block a >> release announcement because of typos unless they've very serious indeed. > I agree. > > A moderation mechanism is not an appropriate way of initiating a conversation. > This approach is rather problematic and doesn't align at all with our > collaborative work flow. > > Dear anonymous robot(?), please use the dev@ list for such purposes, so we > know who is providing feedback and can have an actual conversation together > about whatever might need to be done exactly to satisfy your concerns. > > Thanks :)
So, that anonymous moderator's complaint is doubly silly given that there are currently 4 releases on dist/release and you can only have one file named "KEYS" there. I'm pretty sure downstream users who use the source release are intelligent enough to interpret "KEYS" as "*.KEYS" if necessary. -- Brane
