Re: [mpg123-devel] [mpg123-users] New merged mailing list for mpg123 discussion
Brought to you by:
sobukus
From: Thomas O. <tho...@or...> - 2020-05-11 06:16:30
|
Am Sun, 10 May 2020 23:07:01 +0200 schrieb Martin Guy <mar...@gm...>: > Developers if it regards people (potentially) modifying the code base, > users for people using it […] but not expecting to have to dig into the > source code. Sure, but what's with discussion of possible changes in the code? Developers might have an idea they like, but it would have consequences for users that they did not think about. Users could jump in early in the process. I think that synergy has value that for bigger projects is overshadowed by the issue of high volume of posts. But then, really big projects need further divisions. Try to get a discussion on LKML … or anyone notice your patch proposal at all (I tried, with CC to the maintainer of the portion of code I was patching …)! But back to developer discussions: Frankly, this mostly takes place in IRC (#mpg123 on freenode) or in my head. There are occasional contributions from people that they share, again, often personally to me. Some more complicated issues and patches get communicated to the list. The place for serious developer discussion about definite development issues (bug or feature) is actually the bug tracker. We got already several channels to choose from. > I guess other developers using libmpg123 but not expecting to modify > its internals are "users" in this case. Yes. I do consider people building their applications using the library users of the project. I'm still open for the outcome of this attempted merge. And I hope you have no hard feelings if it does go through. The current subscriber score is this: - mpg123-devel: 21 (-1) - mpg123-users: 29 (-2) - mpg123-discuss: 8 (+8) Most people are still watching the game and stay on the old lists, too. I am keeping this open till the release of mpg123-1.26.0 (so, something like two weeks). The announcement of the release will be on all lists in any case, along with the announcement of mailing list future. If the count of mpg123-discuss is not at least on par with the bigger of the other two (± 5, adjusting for inactive folks), I consider the attempt failed and will remove it again. Alrighty then, Thomas PS: It's a tad ironic that this discussion about separation of discussions is providing a peak of activity for both lists now, with two people being involved;-) |