[Python-modules-team] [Python-modules-commits] [mpmath] 01/01: d/copyright: Changed licence shortname BSD -> BSD-3-clause
Barry Warsaw
barry at debian.org
Sat Apr 30 15:43:40 UTC 2016
On Apr 30, 2016, at 04:10 PM, Sandro Tosi wrote:
>> I'm just going thru Lintian report and fixing few warnings.
>
>but for this yes.
But why get pre-approval for *this* particular commit? Which change do you
have a problem with? I genuinely want to know because I do think we need to
have clear guidelines about what our teammates are allowed to work on.
A while ago, we did hash out the semantics of team in Maintainers vs
Uploaders. Because commits are always reversible, I don't have any problem
with our current rules for team-in-Uploaders. It's the compact we make by
having team maintained packages, and I for one think it's a good trade-off. I
appreciate the help in cleaning up our collective packages.
>well, collaborative work kinda requires agreement on what that work
>would be, and also is not that collaborative to commit whatever you
>see fit and then let somebody else deal with it in a next upload. but
>hey "it's me"...
I think we should generally assume that our teammates know what they're doing
and have the skills and courtesy to follow the rules. I recently noticed that
Ondrej committed some changes to fix our Vcs- urls to https, and I think that
was a nice thing to do!
For a mass change like this, Ondrej should have followed up with an email to
the list. But he wasn't outside the bounds to make the change.
Cheers,
-Barry
More information about the Python-modules-team
mailing list