On 11/12/19 2:38 AM, Sandro Tosi wrote:
> please also realize not everyone shares the
> same ideas as yours and you should try sometimes to respect those
> people decisions too.
With all due respect, the point that I'm trying to make is that this
policy is only there because what I believe is a mi
that policy is well written down, at
https://wiki.debian.org/Teams/PythonModulesTeam/HowToJoin - give it a
look and see if it clarifies your doubt about team maintenance and why
someone would prefer to have the ultimate responsibility for the
quality of a package.
you already created the openstack
On 11/11/19 9:17 PM, Scott Kitterman wrote:
> Personally, I've been judicious in putting myself as Maintainer in DPMT and
> PAPT packages. If we were to ditch the current policy, my immediate response
> would be to remove DPMT/PAPT from uploaders and maintain them outside the
> team. It's abou
On November 10, 2019 10:09:57 PM UTC, Thomas Goirand wrote:
>On 11/10/19 1:20 AM, Sandro Tosi wrote:
>> is there any public trace of these "many voices"?
>
>Just like when we discussed moving away from SVN to Git, we can't know
>the exact number unless we have a kind of poll/vote (but we don't
On 11/11/19 9:21 AM, Fabrice BAUZAC-STEHLY wrote:
> For the record, it looks like this policy comes from the package
> "developers-reference", section "Collaborative maintenance".
Absolutely not. The developers-reference doesn't tell what the Python
team policy is when the Uploaders field contains
Would it be possible to satisfy both groups by having an option on DDPO
and similar listing tools for "only show team-as-Maintainer packages" vs
"also show team-as-Uploader packages"?
i.e. making it convenient for people to use either of these definitions
of "in the team" as they prefer?
For the record, it looks like this policy comes from the package
"developers-reference", section "Collaborative maintenance".
--
Fabrice BAUZAC-STEHLY
PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
On 11/10/19 1:20 AM, Sandro Tosi wrote:
> is there any public trace of these "many voices"?
Just like when we discussed moving away from SVN to Git, we can't know
the exact number unless we have a kind of poll/vote (but we don't
actually *have* to start such poll... I'm just saying it's hard to kn
> On 11/8/19 8:54 AM, intrigeri wrote:
> > - In https://wiki.debian.org/Teams/PythonModulesTeam/HowToJoin,
> > the "Policy About Maintainer and Uploaders Fields" section
> >mentions an "unwritten policy". Said policy seems to have bee
a
>> pleasure to meet you at each debconf.
>>
>> On 11/8/19 8:54 AM, intrigeri wrote:
>>> - In https://wiki.debian.org/Teams/PythonModulesTeam/HowToJoin,
>>>the "Policy About Maintainer and Uploaders Fields" section
>>>menti
AM, intrigeri wrote:
>> - In https://wiki.debian.org/Teams/PythonModulesTeam/HowToJoin,
>>the "Policy About Maintainer and Uploaders Fields" section
>>mentions an "unwritten policy". Said policy seems to have been
>>written since:
>>
>>
owToJoin,
> the "Policy About Maintainer and Uploaders Fields" section
>mentions an "unwritten policy". Said policy seems to have been
>written since:
>
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
It's pr
12 matches
Mail list logo
