Scaling back for now
After the events of April, I've realized that I have a lot less time, and to be frankly honest, motivation for contributing to Debian right now. So I'm scaling back, but not retiring. I've tried to reflect my current level of participation by updating the packages for which I was sole or primary Maintainer, putting DPMT or PAPT in the Maintainer field and moving myself to Uploaders[*]. This reflects my hope that the team will be better able to maintain these packages than I will right now, and should remove me as the single point of failure for their continued improvement in Debian. As per team conventions, this means you don't have to ask my permission to make changes to the packages. If I've missed any, please do let me know. I am not giving up on Debian or Ubuntu! I still feel strongly about their importance and excellence in the open source and free software world, and about their strengths as Linux distributions. I still use them both! And I'm still keenly interested in the migration to Python 3 across the whole Python ecosystem, and Debian in particular. I'll continue to contribute where I can and as time allows. But for now, as my participation in Debian is solely on my own free time, I've found that I have competing interests for that time, and I plan to spend it in other ways. The Debian Python community continues to exemplify the best in collaborative development. DPMT and PAPT are fantastic teams, filled with great people, and smart developers, and I have always felt honored to be part of it. I'm happy to continue to contribute, even if in a more tangential role for now. I'm back on IRC again, so as always, if I can help with anything, please don't hesitate to reach out. Cheers, -Barry [*] I've made the changes in the git repos, but not necessarily uploaded new versions. pgpwPVHzPFQqo.pgp Description: OpenPGP digital signature
Re: Scaling back for now
I just wanted to say thank you for all you've done for Debian & Python. Diane signature.asc Description: This is a digitally signed message part
Re: RFS: jupyter components
Hi, Le 28/08/2017 à 23:56, Gordon Ball a écrit : > Hello > > The following packages should be ready for upload, if someone would be > willing to check and sponsor the uploads: > > * ipython 5.4.0-1 > >IPython 6.x is now available, but is python3 only. For the moment, >the existing ipython source package will be the 5.x series, and at >some point it will cease to build the python3 package and a new >source package based on ipython6 will take that binary over. > >Question for previous packagers: we currently ship a custom >ipython.sh script as /usr/bin/ipython[3] instead of using the >entry-points script that would otherwise be installed, but I can't >find the rationale documented - faster startup? > > * jupyter-console: 5.2.0-1 > >I tried out converting this one to gbp-pq (all others are still in >git-dpm format) > > * jupyter-core: 4.3.0-1 > * nbformat 4.4.0-1 > * jupyter-client: 5.1.0-1 > > > The remaining packages are currently blocked: > > * nbconvert: 5.2.1 > >waiting on python-pandocfilters >= 1.4 (already in dpmt git, but >not yet uploaded) > > * jupyter-notebook: 5.0.0 > >working package available, but with some functionality limited due to >unpackaged or out-of-date javascript libraries I haven't dared touching those packages recently (and especially not updating them to later upstream) precisely because I knew I would risk killing Python2 support. Could you be more explicit about which javascript libraries are unpackaged or out-of-date? I've been struggling since pretty long to keep some of the javascript packages I made for jupyter up to date, so perhaps at one point that effort might help... Snark on #debian-python and #debian-js
RFS: jupyter components
Hello The following packages should be ready for upload, if someone would be willing to check and sponsor the uploads: * ipython 5.4.0-1 IPython 6.x is now available, but is python3 only. For the moment, the existing ipython source package will be the 5.x series, and at some point it will cease to build the python3 package and a new source package based on ipython6 will take that binary over. Question for previous packagers: we currently ship a custom ipython.sh script as /usr/bin/ipython[3] instead of using the entry-points script that would otherwise be installed, but I can't find the rationale documented - faster startup? * jupyter-console: 5.2.0-1 I tried out converting this one to gbp-pq (all others are still in git-dpm format) * jupyter-core: 4.3.0-1 * nbformat 4.4.0-1 * jupyter-client: 5.1.0-1 The remaining packages are currently blocked: * nbconvert: 5.2.1 waiting on python-pandocfilters >= 1.4 (already in dpmt git, but not yet uploaded) * jupyter-notebook: 5.0.0 working package available, but with some functionality limited due to unpackaged or out-of-date javascript libraries Thanks Gordon
Re: Scaling back for now
Barry Warsaw writes: > After the events of April, I've realized that I have a lot less time, > and to be frankly honest, motivation for contributing to Debian right > now. So I'm scaling back, but not retiring. (I don't know what “the events of April” is meant to refer to; if someone can enlighten me – probably in private, or just a pointer to existing discussions I can read – I'd appreciate that.) Thank you, Barry, for recognising when it's time to scale back your involvement, and responsibly handing over authority to continue work. -- \ “Don't worry about what anybody else is going to do. The best | `\ way to predict the future is to invent it.” —Alan Kay | _o__) | Ben Finney
