Re: Getting stuck into apps-team and modules-team
[Jonathan Wiltshire, 2009-08-13]
> I've looked at a few packages in the repositories for these teams, but I'm
> reluctant to start making changes without making sure it's not going to
> upset anybody :)
feel free to commit your changes, we can always revert it ;-)
(you'll get private replies from those subscribed to -commits if
there's something wrong)
> Where the team is just an uploader, I'm inclined to leave the maintainer to
> ask for help when s/he needs it. But where packages are fully under the team's
> scope, is there any protocol for starting work on an oustanding package?
>
> Particularly where there are bugs or new upstreams available, is it acceptable
> to just get stuck in, or is wise to contact the last changer (I found little
> evidence of this on lists, but I may have been looking in the wrong
> places)?
I usually ask via IRC or in private mails
> I'd like to contribute to both teams (so by all means say 'please do this
> for us') but not at the risk of disrupting their workflow.
see this thread:
http://lists.debian.org/debian-python/2008/03/msg00014.html
my reply (and I still use these rules when I do changes in team packages
or when I sponsor team uploads) is here:
http://lists.debian.org/debian-python/2008/03/msg00016.html
--
-=[ Piotr Ożarowski ]=-
-=[ http://www.ozarowski.pl ]=-
Reply to: