On Thu, Jul 28, 2022 at 8:49 PM Hannah von Reth <han...@von-reth.de> wrote:
> Hi Thomas, > Hi Hannah, > > I wanted to request a craft specific ml before but the valid argument was > brought up that we would loose basically everyone already subscribed and it > would be quite lonely on that ml for a while. > It would also mean that I'd need to do a bad job in moderating two ml's > instead of just one... > But yes you are completely correct, the windows ml feels a bit wrong. > One possibility is that we could "rename" the list which while a bit messy is certainly doable. (In essence, you create a new mailing list, copy over the archives and subscriptions and then close the old list) That way there would still be a single list, and given that kde-windows@kde.org has effectively been serving as the Craft mailing list for some time I don't think there should be any major objections to this. Cheers, Ben > > Cheers, > > Hannah > > ------------------------------ > *From:* Kde-windows on behalf of Thomas Friedrichsmeier > *Sent:* Wednesday, July 27, 2022 21:04 > *To:* kde-windows@kde.org > *Cc:* caulier.gil...@gmail.com > *Subject:* A craft mailinglist? Was: [Craft] [Bug 457185] Craft digiKam > MacOS : libgphoto2 packaging problem. > > Am Wed, 27 Jul 2022 06:49:18 +0000 > schrieb "Hannah von Reth" <bugzilla_nore...@kde.org>: > > > https://bugs.kde.org/show_bug.cgi?id=457185 > > [...] > > > Btw, > > This is the craft bug tracker, not stackoverflow or a mailing list. > > Cheers, > > > > Hannah > > I'll take this as an opportunity to mention that I have often thought > craft may need a dedicated mailing list? It has long since out-grown > its Windows-only days. Posting to kde-windows really does feel a bit > misplaced when discussing problems with AppImages or APKs. Also, at > times I have some unfinished thoughts on craft itself that are too > involved for chat, but also don't quite translate into issues or merge > requests. Last not least, where, other than chat, would (usage) > problems with binary-factory infrastructure be discussed? > > Does anybody else see a need for this? And maybe calling it something > like "kde-build" would even encourage more synergy with kde-buildsrc? > > Regards > Thomas >
