On Wed, 30 Sep 2015 at 10:45 Thomas Goirand <z...@debian.org> wrote:

> On 09/29/2015 04:02 PM, Tristan Seligmann wrote:
> > but I'm not sure that having someone
> > blindly upload my packages if they haven't worked on them before is a
> > good idea.
> If this is what you think of my upload, I don't agree with the above
> wording at least.

I don't specifically know anything about networkx, and I didn't take the
time to look at it, so I wasn't directing this at you personally except
insofar as the events that spawned this thread made me think about
situations like this. I think I do owe you an apology as my original mail
was worded carelessly.

On 09/29/2015 04:02 PM, Tristan Seligmann wrote:
> > I feel like I should go through all of my packages and remove the team
> > from Maintainer for all of them
> If you don't want anyone from the team to upload "your" packages (btw,
> they are not yours, you are sharing them with other DDs and all of our
> user bases), then by all means, remove the team from any fields.

They're mine in the sense that I am taking responsibility for them, while
others are not. I'm the one reading the bug repoorts, looking at the
package on my qa.debian.org dashboard, etc. I'm certainly not opposed (in
general) to anyone wants to share that responsibility, but then surely the
way to do this is to add themselves to Uploaders? If they're not interested
in doing that, then I think it's probably best if I (or another
co-maintainer, if there is one!) am at least glancing over their changes
before they're uploaded.

In other words, I'm not trying to say "MINE! ALL MINE! HANDS OFF!", and in
fact I don't mind anyone *committing* things to any of my packages: the
worst case scenario there is that I see the changes, find some horrible
problem, revert them, and let you know why. I don't think that's a terrible
state of affairs at all for a worst case, and most of the time the scenario
will be that I see the changes, don't find any horrible problems, and am
very happy that someone else did some work so that I didn't have to do it!
But I am uncomfortable taking responsibility for a package version that I
didn't even have a chance to look at before it was uploaded.

On the other hand, I don't want a lack of time/effort to hold up others who
can put in the time/effort, that is why I try to make a point out of
responding quickly in cases like this; I know how frustrating it can be to
have a simple patch blocked for weeks by an unresponsive maintainer, and I
definitely don't want my "please don't upload without pinging me" ideas to
lead to situations like that. In other words, if I don't have the time to
respond quickly, then I'm probably disqualifying myself as a maintainer
anyway, so it only makes sense to allow others to take over in my
"absence", even if only temporarily.

Reply via email to