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

Re: Indeed, python-concurrent.futures is the same



On 01/26/2014 01:21 AM, Sandro Tosi wrote:
>> if you don't want the package to be team maintained, perhaps take
>> it out of team maintenance?
> 
> lecturing is not required, thanks

Actually, it seems it's required here. From this page:
https://wiki.debian.org/Teams/PythonModulesTeam/HowToJoin

on chapter "Policy About Maintainer and Uploaders Fields":

"There is a unwritten policy about the usage of Maintainer and Uploaders
field, you might be interested to know about:

If the team is in the Maintainer field (and you are in Uploaders field)
then every member of the team can apply changes to the package and
upload it freely;

if you are in the Maintainer field (and the team is in Uploaders field)
then every member of the team can apply changes to the package but any
upload should be acknowledged by you (there are some exceptions, like
uploads to fix RC bugs, but are infrequent)."

What is it that you don't understand in "the team can apply changes to
the package and upload it freely"?

Thomas


Reply to: