Re: [Python-modules-team] [Python-modules-commits] [mpmath] 01/01: d/copyright: Changed licence shortname BSD -> BSD-3-clause
Hi, CCing list, maybe someone have another opinion. 2016-04-30 16:37 GMT+02:00 Sandro Tosi : > please do not change debian/copyright for the packages I am in the > Maintainer field, thanks > http://anonscm.debian.org/cgit/python-modules/packages/mpmath.git/tree/debian/control#n4 Maintainer: Sandro Tosi Uploaders: Debian Python Modules Team < python-modules-team@lists.alioth.debian.org> so according to: http://python-modules.alioth.debian.org/policy.html 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. Package I commited to is team maintained. If you don't want anyone commit to it, why is it inside DPMT? I'm not going to upload it without prior authorization from you. I'm sorry, but it's impossible to me to make list of "bans packages" or "banned maintainer". Thank you. -- Best regards Bc. Ondrej Novy ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
Re: [Python-modules-team] [Python-modules-commits] [mpmath] 01/01: d/copyright: Changed licence shortname BSD -> BSD-3-clause
so eventually you could declare your intention of "fixing debian/copyright" to the list before starting this operation? On Sat, Apr 30, 2016 at 3:49 PM, Ondrej Novy wrote: > Hi, > > CCing list, maybe someone have another opinion. > > 2016-04-30 16:37 GMT+02:00 Sandro Tosi : >> >> please do not change debian/copyright for the packages I am in the >> Maintainer field, thanks > > > http://anonscm.debian.org/cgit/python-modules/packages/mpmath.git/tree/debian/control#n4 > Maintainer: Sandro Tosi > Uploaders: Debian Python Modules Team > > > so according to: http://python-modules.alioth.debian.org/policy.html > > 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. > > Package I commited to is team maintained. If you don't want anyone commit to > it, why is it inside DPMT? I'm not going to upload it without prior > authorization from you. > > I'm sorry, but it's impossible to me to make list of "bans packages" or > "banned maintainer". > > Thank you. > > -- > Best regards > Bc. Ondrej Novy -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
Re: [Python-modules-team] [Python-modules-commits] [mpmath] 01/01: d/copyright: Changed licence shortname BSD -> BSD-3-clause
Hi, 2016-04-30 16:51 GMT+02:00 Sandro Tosi : > so eventually you could declare your intention of "fixing > debian/copyright" to the list before starting this operation? > so should I send mail to mailing list before any intention to commit anything? :) I'm just going thru Lintian report and fixing few warnings. If you have any concerns about my change(s), just ping me on IRC or via email/mailing list with explanation where you see problem. But don't send me "don't not touch, it's me" email please - that's not how collaborative work should work. Thanks. -- Best regards Bc. Ondrej Novy ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
Re: [Python-modules-team] [Python-modules-commits] [mpmath] 01/01: d/copyright: Changed licence shortname BSD -> BSD-3-clause
On Sat, Apr 30, 2016 at 4:04 PM, Ondrej Novy wrote: > Hi, > > 2016-04-30 16:51 GMT+02:00 Sandro Tosi : >> >> so eventually you could declare your intention of "fixing >> debian/copyright" to the list before starting this operation? > > > so should I send mail to mailing list before any intention to commit > anything? :) no. > > I'm just going thru Lintian report and fixing few warnings. but for this yes. > If you have any > concerns about my change(s), just ping me on IRC or via email/mailing list > with explanation where you see problem. But don't send me "don't not touch, > it's me" email please - that's not how collaborative work should work. 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"... -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
Re: [Python-modules-team] [Python-modules-commits] [mpmath] 01/01: d/copyright: Changed licence shortname BSD -> BSD-3-clause
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 ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
Re: [Python-modules-team] [Python-modules-commits] [mpmath] 01/01: d/copyright: Changed licence shortname BSD -> BSD-3-clause
On Sat, Apr 30, 2016 at 4:43 PM, Barry Warsaw wrote: > 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? the point is not for this specific commit (and I jbrought this up to him once i got this email as it was the second package I am maintainer for receiving this change) > Which change do you have a problem with? debian/copyright is a rather delicate (and sometimes annoying, let's face it) file, a change to it requires the one doing the upload to actually check that what's been updated actually matches reality, which is just extra/unplanned work > 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. yeah but changing copyright is a little bit more intrusive than fixing a typo or s/http/https/ > >>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. like we assume with sponsorees, but still we double check everything they do > 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! and in fact i havent said anything (even if it could have been announced to the list and the commit message could have been a *lot* better, but that might be categorized as nitpicking) > 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. -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
Re: [Python-modules-team] [Python-modules-commits] [mpmath] 01/01: d/copyright: Changed licence shortname BSD -> BSD-3-clause
Hi, 2016-04-30 17:57 GMT+02:00 Sandro Tosi : > debian/copyright is a rather delicate (and sometimes annoying, let's > face it) file, a change to it requires the one doing the upload to > actually check that what's been updated actually matches reality, > which is just extra/unplanned work > so you don't want to check my change before upload, because it's extra work. You are saying d/copyright change should be checked harder than d/rules change for example? I think uploader/sponsor should hard check ALL changes. There isn't any more delicate part of package. If you don't want check d/copyright, just revert my commit(s) before upload. That's git for. You are uploader, so you make decision what you upload. If you don't want do this, just change Uploader field to team and someone will do it for you :) yeah but changing copyright is a little bit more intrusive than fixing > a typo or s/http/https/ > it's just point of view. More intrusive is "completly rewrite d/rules" for me. I renamed shortname to match https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ which removed Lintian warning, that's all. and in fact i havent said anything (even if it could have been > announced to the list and the commit message could have been a *lot* > better, but that might be categorized as nitpicking) > announced before: http://lists.alioth.debian.org/pipermail/python-modules-team/2016-March/030256.html Be constructive now please: Do you found any really problem/bug in my commit(s)? If yes, send it to me and i will fix it. Thanks. -- Best regards Bc. Ondrej Novy ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
Re: [Python-modules-team] [Python-modules-commits] [mpmath] 01/01: d/copyright: Changed licence shortname BSD -> BSD-3-clause
On Apr 30, 2016, at 07:21 PM, Ondrej Novy wrote: >announced before: >http://lists.alioth.debian.org/pipermail/python-modules-team/2016-March/030256.html Thanks! I must have missed it, but you did the right thing. -Barry PS: why do we have two mailing lists?! :( :( pgp3FKxlJshFs.pgp Description: OpenPGP digital signature ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
Re: [Python-modules-team] [Python-modules-commits] [mpmath] 01/01: d/copyright: Changed licence shortname BSD -> BSD-3-clause
Barry Warsaw writes: >>announced before: >>http://lists.alioth.debian.org/pipermail/python-modules-team/2016-March/030256.html > > Thanks! I must have missed it, but you did the right thing. In future, far better to use the debian-pyt...@lists.debian.org mailing list; less likely to get missed. Having said that I did see the email, and I was happy with it. I didn't notice it was the wrong mailing list though :-(. It does cause confusion for people who are familar with the team, having the aloith as the Maintainer field - people use this expecting to be able to contact the Maintainer... Sometimes I will resend emails to debian-pyt...@lists.debian.org when I see this happen. -- Brian May ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
