I agree with Crystal that an e-mail driven workflow is preferable. >From an efficiency perspective, I have no opinion on e-mail patches vs github-style pull requests, but from a practical one, I think e-mail is superior because it filters out a lot of noise. Github has been so gamified that randos will push utter crap on you just to make one of their dots green.
That, along with the hurdle of accepting mailing list noise into one's inbox, are excellent ways of filtering out the drive-bys. JS On 26-01-06 11:03, Crystal Kolipe via Mutt-dev wrote: > On Tue, Jan 06, 2026 at 10:35:24AM +0800, Kevin J. McCarthy wrote: > > Four years later, I'm struggling mightily to find the time (and enthusiasm) > > to keep at it anymore. > > Thanks for the work you've done on mutt over the years. > > > As to the "dead" mailing list. Part of this is due to the move to GitLab > > years ago. When that happened, a lot more PR and tickets were created and > > handled there, and so less and less on this mailing list. > > I don't want to divert this thread in to a discussion of the merits of > different platforms, but this move does probably explain at least some of the > slow-down in the mutt development community. > > There is an arguably small but significant demographic of developers who are > mostly involved with projects that are mailing list centric. Anything that > doesn't arrive as a plain text email with a patch attached requires me to > break my workflow, so in practical terms it will always be given a lower > priority. > > I accept that for other developers, platform foo might be the 'normal', and > dealing with diff and patch breaks their workflow. But at the end of the day, > mutt is an email client, so it seems logical to me that development would be > list-focused. > > > Another discussion might also take place about whether that is the approach > > Mutt wants going forward. I have reserved a "mutt" account on sr.ht, which > > could be an alternative place to host the repos, and switch back to mailing > > list patch review completely (either continuing on the OSUOSL lists, or via > > sr.ht mailing list) if desired. > > Be careful not to end up with a list flooded with automatic messages from the > source management system. I'm subsribed to a handful on which about 90% of > the traffic is just an endless combination of: > > Thanks, applied! > Patch foo committed! > Automatic build SUCCESS! > Automatic build FAILED. > > ... there is so much noise that any real discussion, (which is mostly done > elsewhere anyway), is just lost.
