Hi Jonas,Heads up: I've not been very active in the team for a long time, so my views might only have historical relevance.
Just as a general rule of thumb, traditionally we tried to keep discussion emails on debian-haskell@lists.debian.org and packaging noise on pkg-haskell-maintainers@lists.alioth.debian.org.
Am 25.11.22 um 12:01 schrieb Jonas Smedegaard:
Hmm, I guess that explains how I have not been bombarded with Haskell packaging noise till now. How do others handle that? I mean, I would obviously like to receive bugreports for pandoc, but opening a firehose for all Haskell packages will mean that I am quite likely to miss relevant posts, since I am not really involved in most work in the Haskell team.
I'd say the way I handled it is “poorly”. When I was active in the team, I mostly tried to care about the whole package set, so filtering out certain packages was usually not a concern for me. But it also means I receive so many bug reports about Haskell packages, that I perceive them mostly as noise. When I wanted to look at bug reports, I usually did it via the web interface by filtering for packages maintained by the team.
This isn't a great solution, because it doesn't give me the opportunity to reply to new bug reports in a timely manner, which might be frustrating for the reporters. But so far I haven't come up with a better solution on how to deal with the amount of maintainer emails we receive.
Perhaps even framing it like that as "I don't really care about teamwork activities" is an indication that I should move my few Haskell packages out of the team. What do others think? Are there benefits for the team in having me here, with the way I do only very focused work on few packages?
I think it could be beneficial, as long as it doesn't bring other implicit consequences with it. From what I've seen, the arrangement that you mostly care about a limited package set, works well enough. There's a lot of coordination required in maintaining the Haskell packages, but usually you do coordinate with others and use the appropriate coordination tools used by the team. I think this can stay the way it is.
I think changing the maintainer entries for your packages to you personally, can be beneficial, since it allows you to focus more closely on changes to your packages and provide better responsiveness to your users. But it shouldn't mean that you separate the work you do more from the team, the coordination and collaboration that's been working so far should stay the same.
TL;DR if you think changing the maintainer addresses of your packages helps you deal with them, go for it, but try not to take it as a reason to reduce the ongoing collaboration with the rest of the team.
Regards Sven
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature