Re: modifications by sponsors
Andrew Starr-Bochicchio <a.starr.b@gmail.com> writes:
> Personally, I feel that when adding a new package to the archive it can
> actually be very useful to make the contributor jump through all the
> hoops so they understand the level of responsibly involved with becoming
> a package maintainer. If you're sponsoring say a NMU RC bug fix, and
> there is some minor issue (like perhaps unnecessarily bumping the
> standards version or a typo in the changelog), I'd say go ahead make the
> change, upload, and then describe exactly why you had to do what you did
> so the contributor will know next time.
I've always taken the time to ask the sponsee first if making the change
is okay. Usually people don't mind, and it rarely takes much time to get
a response, so it's not much of a delay. I don't know that it's
necessarily *required*, but it felt to me like a simple and meaningful
courtesy.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: