Bug#800903: ITP: jupyter-client -- Jupyter protocol client APIs

2015-10-04 Thread Julien Puydt
Package: wnpp Severity: wishlist X-Debbugs-CC: debian-python@lists.debian.org * Package name: jupyter-client Version : 4.0.0 Upstream Author : Jupyter Development Team * URL : https://github.com/jupyter/jupyter_client * License : BSD-3-clause Programming Lang

Re: Git migration schedule

2015-10-04 Thread Sandro Tosi
On Sat, Oct 3, 2015 at 7:52 PM, Stefano Rivera wrote: > The errors: > > Cannot "git-dpm init" package: adhocracy [8<] > Cannot "git-dpm init" package: urlgrabber those are 98 packages > I think these are mostly because the package has never been uploaded to > Debian, or has a new release staged,

Re: Git migration schedule

2015-10-04 Thread Julien Puydt
Hi, Le dimanche 04 oct. 2015 à 20:03:29 (+0100), Sandro Tosi a écrit : > am I the only one thinking it's quite a huge number to be handled by > hand? and whose hands will be the ones converting these packages? > yours or Barry's dont seem enough and others will need training/time. There's a point

Re: Git migration schedule

2015-10-04 Thread Sandro Tosi
sorry, i forgot to ask another question: how will the packages already maintained in git be handled? On Sun, Oct 4, 2015 at 8:03 PM, Sandro Tosi wrote: > On Sat, Oct 3, 2015 at 7:52 PM, Stefano Rivera wrote: >> The errors: >> >> Cannot "git-dpm init" package: adhocracy > [8<] >> Cannot "git-dpm

Re: Git migration schedule

2015-10-04 Thread Stefano Rivera
Hi Sandro (2015.10.04_21:03:29_+0200) > and other 9, for a grand total of 109 packages that cannot be > converted to git, 13.5% of DPMT (oh, what about PAPT?) They're all converted. There are just some remaining steps to do by hand, to reconcile the SVN history with upstream history, and convert p

Re: Git migration schedule

2015-10-04 Thread Stefano Rivera
Hi Sandro (2015.10.04_21:31:07_+0200) > sorry, i forgot to ask another question: how will the packages already > maintained in git be handled? Up to their maintainers (assuming they're following team standards). If people only have one git package, for testing, each, then this shouldn't be an issu

Re: [DPMT] radical changes: automation, carrot and stick

2015-10-04 Thread Stefano Rivera
This thread has had me thinking a bit. Hi Scott (2015.10.02_20:34:16_+0200) > Personally, I like the current approach where someone can either commit to > either strong team maintainership (DPMT in maintainer) or weak team > involvement (DPMT as uploader). If you'll check, I have done both and

Re: [DPMT] radical changes: automation, carrot and stick

2015-10-04 Thread Brian May
On Mon, 5 Oct 2015 at 08:54 Stefano Rivera wrote: > There's a fundamental question to ask here. Do we want to welcome Python > packages into the team, or do we want to put up barriers and require a > level of commitment before packages can be brought into the team? Speaking for myself, I welcom