On 31 May 2015 at 19:36, Reinhard Tartler <siret...@gmail.com> wrote: > IMO, if there is no need for team commitment, then there is no need > for the package to be under team maintenance in the first place. In > this case, it really doesn't matter if the package has a dedicated > maintainer or a team with a single uploader in the field.
I disagree. There is a large range of options between "fully active on package maintenance" and "don't even look at the package". As Fabian says, we do comment on each others bugs from time to time even if we are not formally tied to each package. I have received useful feedback on plenty of bugs. I have tried to provide same when possible and time permits. When I have more time, I look at the commits list and see if something could be improved, even if I have nothing to do with the package. I have even investigated bugs on packages that I am not an Uploader in. I would certainly do no such thing for packages not in the team umbrella, because: 1. I already have enough lists to subscribe to yet another one 2. By being a member of the team, there is an implicit ack to the idea of receiving "unsolicited" feedback from others, which is not the case otherwise. Last, but not least, having the package in the team makes it easier to solicit feedback (even if it does not come as readily as one would hope sometimes). I conclude the barriers to cross-contributions are greatly reduced by just having related packages in a single team. -- Saludos, Felipe Sateler _______________________________________________ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
