Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #7338
| From | Barry Warsaw <barry@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental |
| Date | 2015-09-29 15:50 +0200 |
| Message-ID | <qe3s8-85D-57@gated-at.bofh.it> (permalink) |
| References | <qe1gC-53J-13@gated-at.bofh.it> <qe1gC-53J-11@gated-at.bofh.it> |
| Organization | The Organization of Unorganized Woozalists |
On Sep 29, 2015, at 12:26 PM, Sandro Tosi wrote: >Once again, the python policy about Maintainer/Uploaders has been ignored > >either policy changes or this has to stop at some point. A few observations. The policy should perhaps be better promoted or more explicitly written. The links you provided are useful, but I wonder whether they are easily overlooked, forgotten, or misinterpreted. Policy doesn't really spell out the operational differences for when the team is Maintainer vs. Uploader, and the wiki page explicitly says it's an *unwritten* policy (despite the fact that putting it in the wiki probably qualifies as "written" :). How should the change be acknowledged by the maintainer? Should I Cc the mailing list when I contact the maintainer? Is it okay to commit to vcs but not upload? How long do you wait for feedback before you can do the upload? (Aside: git! I would love to be able to commit and push a branch and then ask for the maintainer to review, merge, and upload - or give me the green light to go ahead.) Should we have some automated tools to help out here? I'm not sure where to hook in such a tool, but if for example when I build a source package, I got a nice little lintian-like warning saying "The package is team uploadable but not team maintained, did you give the maintainer time to respond to your issue?" Something like that would go a long way toward mitigating accidental or careless toe-stepping. Do all team members understand the implications when they set the two fields? Some maintainers may not really care and may have been less conscientious about setting the fields. The wiki says that the general rule of thumb is to set the team as Maintainer, to which I agree. I may not have been as deliberate about my own packages, so I plan on reviewing them, and will fix any that aren't "special". Cheers, -Barry
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Sandro Tosi <morph@debian.org> - 2015-09-29 13:30 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Piotr Ożarowski <piotr@debian.org> - 2015-09-29 13:50 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Julien Cristau <julien.cristau@logilab.fr> - 2015-09-29 14:00 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Sandro Tosi <morph@debian.org> - 2015-09-29 14:20 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Thomas Goirand <zigo@debian.org> - 2015-09-30 10:20 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Sandro Tosi <morph@debian.org> - 2015-09-30 10:50 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Scott Kitterman <debian@kitterman.com> - 2015-09-29 14:30 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Barry Warsaw <barry@debian.org> - 2015-09-29 15:50 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Tristan Seligmann <mithrandi@mithrandi.net> - 2015-09-29 16:30 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Barry Warsaw <barry@debian.org> - 2015-09-29 16:40 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Thomas Goirand <zigo@debian.org> - 2015-09-30 10:50 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Tristan Seligmann <mithrandi@mithrandi.net> - 2015-09-30 14:10 +0200
Maintainer vs. Uploaders Piotr Ożarowski <piotr@debian.org> - 2015-09-29 16:40 +0200
Re: Maintainer vs. Uploaders Barry Warsaw <barry@debian.org> - 2015-09-29 20:40 +0200
Re: Maintainer vs. Uploaders Sandro Tosi <morph@debian.org> - 2015-09-30 11:30 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Julien Puydt <julien.puydt@laposte.net> - 2015-09-29 17:50 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Barry Warsaw <barry@debian.org> - 2015-09-29 20:40 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Piotr Ożarowski <piotr@debian.org> - 2015-09-29 20:50 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Julien Puydt <julien.puydt@laposte.net> - 2015-09-29 21:00 +0200
lintian and team uploads Piotr Ożarowski <piotr@debian.org> - 2015-09-29 21:50 +0200
Re: lintian and team uploads Barry Warsaw <barry@debian.org> - 2015-09-29 22:00 +0200
Re: lintian and team uploads Julien Puydt <julien.puydt@laposte.net> - 2015-09-29 22:40 +0200
Re: lintian and team uploads Barry Warsaw <barry@debian.org> - 2015-09-29 22:50 +0200
Re: lintian and team uploads Scott Kitterman <debian@kitterman.com> - 2015-09-30 05:00 +0200
Re: lintian and team uploads Scott Kitterman <debian@kitterman.com> - 2015-09-30 05:00 +0200
git migration (AKA missing old good svn days) Piotr Ożarowski <piotr@debian.org> - 2015-09-29 23:10 +0200
Re: git migration (AKA missing old good svn days) Barry Warsaw <barry@debian.org> - 2015-09-30 00:00 +0200
Re: git migration (AKA missing old good svn days) Scott Kitterman <debian@kitterman.com> - 2015-09-30 05:00 +0200
Re: git migration (AKA missing old good svn days) Vincent Bernat <bernat@debian.org> - 2015-09-30 07:40 +0200
Re: git migration (AKA missing old good svn days) Stefano Rivera <stefanor@debian.org> - 2015-10-03 11:40 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Thomas Goirand <zigo@debian.org> - 2015-09-30 11:00 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Sandro Tosi <morph@debian.org> - 2015-09-30 11:20 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Thomas Goirand <zigo@debian.org> - 2015-09-30 17:30 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Thomas Goirand <zigo@debian.org> - 2015-09-30 17:50 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Thomas Kluyver <thomas@kluyver.me.uk> - 2015-09-30 11:30 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Dimitri John Ledkov <xnox@debian.org> - 2015-09-30 12:30 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Sandro Tosi <morph@debian.org> - 2015-09-30 12:50 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Thomas Goirand <zigo@debian.org> - 2015-09-30 17:30 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Andrey Rahmatullin <wrar@debian.org> - 2015-09-30 17:50 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Thomas Goirand <zigo@debian.org> - 2015-09-30 18:10 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Sandro Tosi <morph@debian.org> - 2015-09-30 18:40 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Sandro Tosi <morph@debian.org> - 2015-09-30 12:50 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Scott Kitterman <debian@kitterman.com> - 2015-09-30 13:10 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Scott Kitterman <debian@kitterman.com> - 2015-09-30 12:50 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Thomas Goirand <zigo@debian.org> - 2015-09-30 17:20 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Sandro Tosi <morph@debian.org> - 2015-09-30 18:30 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Michael Fladischer <fladi@debian.org> - 2015-10-05 10:00 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Thomas Goirand <zigo@debian.org> - 2015-10-05 15:00 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Scott Kitterman <debian@kitterman.com> - 2015-10-05 17:00 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Barry Warsaw <barry@debian.org> - 2015-10-05 23:30 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Thomas Goirand <zigo@debian.org> - 2015-10-05 23:50 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Scott Kitterman <debian@kitterman.com> - 2015-10-06 00:40 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Thomas Goirand <zigo@debian.org> - 2015-10-06 01:10 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Scott Kitterman <debian@kitterman.com> - 2015-10-06 02:20 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Thomas Goirand <zigo@debian.org> - 2015-10-06 09:30 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Scott Kitterman <debian@kitterman.com> - 2015-10-06 13:50 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Thomas Goirand <zigo@debian.org> - 2015-10-06 15:40 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Piotr Ożarowski <piotr@debian.org> - 2015-10-06 18:30 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Thomas Goirand <zigo@debian.org> - 2015-10-06 22:50 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Piotr Ożarowski <piotr@debian.org> - 2015-10-06 23:40 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Thomas Goirand <zigo@debian.org> - 2015-10-07 15:40 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Brian May <brian@microcomaustralia.com.au> - 2015-10-07 23:50 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Piotr Ożarowski <piotr@debian.org> - 2015-10-08 00:10 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Thomas Goirand <zigo@debian.org> - 2015-10-06 11:00 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Ben Finney <ben+debian@benfinney.id.au> - 2015-10-06 11:20 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Brian May <brian@microcomaustralia.com.au> - 2015-10-06 02:50 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Scott Kitterman <debian@kitterman.com> - 2015-10-06 03:40 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Thomas Goirand <zigo@debian.org> - 2015-10-06 13:30 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Sandro Tosi <sandro.tosi@gmail.com> - 2015-10-06 13:40 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Jeremy Stanley <fungi@yuggoth.org> - 2015-10-06 03:30 +0200
Re: mock 1.2 breaking tests (was: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental) Thomas Goirand <zigo@debian.org> - 2015-10-06 09:30 +0200
Re: mock 1.2 breaking tests (was: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental) Jeremy Stanley <fungi@yuggoth.org> - 2015-10-06 16:00 +0200
Re: mock 1.2 breaking tests (was: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental) Ian Cordasco <graffatcolmingov@gmail.com> - 2015-10-06 17:50 +0200
Re: mock 1.2 breaking tests Thomas Goirand <zigo@debian.org> - 2015-10-06 19:10 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Robert Collins <robertc@robertcollins.net> - 2015-10-05 20:10 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Barry Warsaw <barry@debian.org> - 2015-10-05 23:20 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Thomas Goirand <zigo@debian.org> - 2015-10-06 09:40 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Barry Warsaw <barry@debian.org> - 2015-10-05 23:20 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Mattia Rizzolo <mattia@mapreri.org> - 2015-10-05 23:20 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Barry Warsaw <barry@debian.org> - 2015-10-05 23:30 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Mattia Rizzolo <mattia@mapreri.org> - 2015-10-05 23:50 +0200
Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental Scott Kitterman <debian@kitterman.com> - 2015-10-05 23:30 +0200
Re: managing transitions (was: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental) Thomas Goirand <zigo@debian.org> - 2015-10-06 09:50 +0200
Re: managing transitions (was: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental) Brian May <brian@microcomaustralia.com.au> - 2015-10-06 10:50 +0200
Re: managing transitions (was: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental) Mattia Rizzolo <mattia@mapreri.org> - 2015-10-06 13:10 +0200
Re: managing transitions Thomas Goirand <zigo@debian.org> - 2015-10-06 16:10 +0200
Re: managing transitions Mattia Rizzolo <mattia@mapreri.org> - 2015-10-06 17:10 +0200
Re: managing transitions (was: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental) Barry Warsaw <barry@debian.org> - 2015-10-06 17:50 +0200
Re: managing transitions Thomas Goirand <zigo@debian.org> - 2015-10-06 19:10 +0200
Re: managing transitions Barry Warsaw <barry@debian.org> - 2015-10-06 20:20 +0200
Re: managing transitions Fred Drake <fred@fdrake.net> - 2015-10-06 21:20 +0200
Re: managing transitions Barry Warsaw <barry@debian.org> - 2015-10-06 21:30 +0200
Re: managing transitions Ian Cordasco <graffatcolmingov@gmail.com> - 2015-10-06 21:30 +0200
csiph-web