multiple uploaders

[Reinhard Tartler]

On Jun 1, 2015 7:11 AM, "Felipe Sateler" <fsateler at debian.org> wrote:
>
> On 31 May 2015 at 19:36, Reinhard Tartler <siretart at 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.

Thank you and Fabian for detailing your positions so clearly.

Apparently has already grown quite big, and the addition of a package to
the the team has become only a small increment in the demand of team
resources. I count Fabian's suggestion to categorize our team packages as
indication for that.

Felipe, generalizing your line of argumentation, we should put all packages
in Debian in a single team, and have all bugs go to a common mailing list
that everyone reads. I believe there even is a mailing list for that. This
clearly doesn't scale, but what is a reasonable limit? I have the
impression that we are already way past that limit, and we have entered a
mode of operation that the Debian QA team does for orphaned packages.

I don't think I have any new input to add to this discussion. The majority
of participants seem to think that the "two uploaders rule" is not useful
as it hinders the adoption of new packages. While, I found this a desirable
property, I also realize that the majority disagrees.

In the end, dropping the rule probably won't make much of a difference
anyways, because it is hardly enforced. So I'm okay with dropping it as an
act to align rules with reality.

Thanks to everyone who provided input on this topic!

Reinhard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20150601/855d7131/attachment-0001.html>