[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Team upload policy

The Python Team policy looks sensible to me.
Any member of the team should be able to fix and upload any team package in general. That helps spread the load and keeps the packages fresh.
But reasonable also to have a stronger oversight model (the weak collaboration case) if a particular package is more tricky and needs more care.
The LowNMU mechanism sounds more awkward, more fiddly to make sure the right setting is used. Not so natural. 

Drew

On 2021-09-16 12:05, Timo Röhling wrote:

Hi,

I was wondering if the Science Team has a policy regarding team
uploads. The reason I'm asking is that there are a few packages
which need a minor fix to make the autopkgtests work again after the
recent CMake upload.

For example, the Python Team has an explicit rule in their team
policy [1]:

* Team in Maintainers is a strong statement that fully collaborative
  maintenance is preferred. Anyone can commit to the Git repository
  and upload as needed. A courtesy email to Uploaders can be nice
  but not required.

* Team in Uploaders is a weak statement of collaboration. Help in
  maintaining the package is appreciated, commits to the Git
  repository are freely welcomed, but before uploading, please
  contact the Maintainer for the green light.


Maybe this is something that we as a team could also adopt? It does
not have to be exactly the same policy, maybe we could just have
something similar to the LowNMU list for the preferred level of
collaboration at some well-known URI.

Cheers
Timo
[1] https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#maintainership
Reply to: