"Files" <files@poetryunlimited.com> writes:
> In light of the recent events, I were to ask Patrick to update a
> segment of the Mandrake RPM build set that is directly impacted by
> and depends on his javahl update which he just recently put in, is
> there an issue to asking Patrick to making this update? Or should it
> go through someone else?
In my opinion, a committer A with even partial commit priveleges is
free to permit another committer B (perhaps with partial priveleges to
another segment of the tree) to make changes to committer A's
area, so long as it is made clear (perhaps in the log message, but
definitely on the list) that committer B did so with the explicit
permission of committer A -- and understanding that committer A is now
accepting a portion of the responsibility of any negative fallout from
that commit. In other words, this is another form of "sponsorship",
similar that which is described in HACKING.
> Patrick's concern was that since he has access rights on the java
> bindings area, he did not want to impose on the maintainer of the
> Mandrake RPMs.
>
> Understandable and laudable. I commend him for his discretion.
As do I.
> However, since I was the last maintainer of the Mandrake RPMs, but
> no longer have commit rights, does that mean that ownership of the
> Mandrake RPM build set reverts to the previous owner or is it still
> under my care, with help from the list, or what?
Not sure there is precedent here. If you no longer wish to be the
maintainer of the Mandrake RPMs, then I suppose it is the
responsibility of the remaining committers to ask the previous owner
of that area if he wants to resume the role. If he does not, the area
will be owned by the remaining committers, and maintained at whatever
granularity of time they can afford to give it.
That said, though you have no commit priveleges, you are free to ask
Patrick (in this case) to submit a patch for the RPM area (since he is
not supposed to commit directly to it), and then as a person with
experience in the affected area of the repository, you can review his
patch, and/or nudge the remaining committers to review and commit that
patch.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Sep 29 18:40:46 2003