Crystal Kolipe via Mutt-dev (2026/01/06 11:03 +0000): > Thanks for the work you've done on mutt over the years.
+1 > > 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. Usually I am always the one who sounds old-fashionned, so perhaps for once let me take the cool-kid side, just for the sake of letting me experiment how it feels. Further down in your email, you were mentionning the fact that today's development implies a lot of noise and I certainly agree with that. The advantage I can see in things like GitHub, though, is that you have the option to opt-out of threads. Which you don't have with a mailing-list. I know Mutt makes itpossible to deal with threads at once, but (1) dealing with threads is bound to displaying the thread structure, which for me as blind is super inconvenient. So I have threads disabled and thus can't take advantage of them, unless of course I am missing osmething. But even if I was able to remove whole threads, I would have to do it repeatedly as soon as new emails from a thread I do not want to follow are arriving. There are many things I struggle with on GitHub, even more on other git-based platforms, but TBH being able to just push and pull branches is something I find convenient. But I certainly realise this is a matter of tastes and it's not something I would want to impose over anybody. Also, dealing with patches through e-mails is certainly something I can learn and would actually be proud to know how to do. But still, at least for the developemnt, don't we want to use tools people arealready familiar with (I am talking aobut branches and merge/pull requests here). Apart from Linux's kernel, are there that many projects that still use lists to share and review code? Seb.
