Bug#818107: [Python-apps-team] Bug#818107: The future of DocOnce
> - Is the required version of all the packages listed in [1] known? I assume the most recent versions should work. To my knowledge, there's no overview of the exact version required. > - Can any of the above mentioned packages be considered optional? I would say that all the packages mentioned, with the exceptions of publish, pygments-ipython-console and pygments-doconce, could be considered optional. > - Is any of the aforementioned projects packaged under a non-obvious name? Not that I know of > - Particularly, is the ipython pygment lexer contained in some > ipython/jupyter package? It's just a wrapper around the lexer included with IPython, so I don't think so. Kristian From: Klaus Zimmermann <klaus_zimmerm...@gmx.de> Sent: 23 November 2016 12:16 To: Francesco Poli; 818...@bugs.debian.org; Kristian Gregorius Hustad Subject: Re: [Python-apps-team] Bug#818107: The future of DocOnce Hi, this looks like an interesting project indeed. As a first step I went through the list of dependencies that Kristian provided. The situation might not be so grim. Unfortunately, there is no information about the actually required versions, but for a number of packages a manual update over the available distribution version seems to have been necessary. For now I just collected those packages, that are not available in Debian at all. If version bumps for existing packages turn out to be necessary, let's deal with that later. The list is: Publish: - pip install -e hg+https://bitbucket.org/logg/publish#egg=publish Sphinx themes: - pip install -e hg+https://bitbucket.org/miiton/sphinxjp.themes.solarized#egg=sphinxjp.themes.solarized - pip install -e git+https://github.com/shkumagai/sphinxjp.themes.impressjs#egg=sphinxjp.themes.impressjs - pip install -e git+https://github.com/kriskda/sphinx-sagecell#egg=sphinx-sagecell Runestone: - pip install sphinxcontrib-paverutils - pip install cogapp - pip install -e git+https://bitbucket.org/hplbit/pygments-ipython-console#egg=pygments-ipython-console - pip install -e git+https://github.com/hplgit/pygments-doconce#egg=pygments-doconce Questions: Kristian: - Is the required version of all the packages listed in [1] known? - Can any of the above mentioned packages be considered optional? Anyone: - Is any of the aforementioned projects packaged under a non-obvious name? - Particularly, is the ipython pygment lexer contained in some ipython/jupyter package? Cheers Klaus [1] https://github.com/hplgit/doconce/blob/master/doc/src/manual/debpkg_doconce.txt On 07/11/2016 21:57, Francesco Poli wrote: > On Mon, 7 Nov 2016 17:03:07 + Kristian Gregorius Hustad wrote: > >> Version 1.0.0 is now listed at https://github.com/hplgit/doconce/releases > > That's awesome, thanks a lot! :-) > > Now I hope the Debian Python Applications Packaging Team will consider > packaging it... > > > > ___ > Python-apps-team mailing list > python-apps-t...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-apps-team >
Bug#818107: [Python-apps-team] Bug#818107: The future of DocOnce
Hi, this looks like an interesting project indeed. As a first step I went through the list of dependencies that Kristian provided. The situation might not be so grim. Unfortunately, there is no information about the actually required versions, but for a number of packages a manual update over the available distribution version seems to have been necessary. For now I just collected those packages, that are not available in Debian at all. If version bumps for existing packages turn out to be necessary, let's deal with that later. The list is: Publish: - pip install -e hg+https://bitbucket.org/logg/publish#egg=publish Sphinx themes: - pip install -e hg+https://bitbucket.org/miiton/sphinxjp.themes.solarized#egg=sphinxjp.themes.solarized - pip install -e git+https://github.com/shkumagai/sphinxjp.themes.impressjs#egg=sphinxjp.themes.impressjs - pip install -e git+https://github.com/kriskda/sphinx-sagecell#egg=sphinx-sagecell Runestone: - pip install sphinxcontrib-paverutils - pip install cogapp - pip install -e git+https://bitbucket.org/hplbit/pygments-ipython-console#egg=pygments-ipython-console - pip install -e git+https://github.com/hplgit/pygments-doconce#egg=pygments-doconce Questions: Kristian: - Is the required version of all the packages listed in [1] known? - Can any of the above mentioned packages be considered optional? Anyone: - Is any of the aforementioned projects packaged under a non-obvious name? - Particularly, is the ipython pygment lexer contained in some ipython/jupyter package? Cheers Klaus [1] https://github.com/hplgit/doconce/blob/master/doc/src/manual/debpkg_doconce.txt On 07/11/2016 21:57, Francesco Poli wrote: > On Mon, 7 Nov 2016 17:03:07 + Kristian Gregorius Hustad wrote: > >> Version 1.0.0 is now listed at https://github.com/hplgit/doconce/releases > > That's awesome, thanks a lot! :-) > > Now I hope the Debian Python Applications Packaging Team will consider > packaging it... > > > > ___ > Python-apps-team mailing list > python-apps-t...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-apps-team > signature.asc Description: OpenPGP digital signature
Bug#818107: The future of DocOnce
On Mon, 7 Nov 2016 21:57:11 +0100 Francesco Poli wrote: [...] > Now I hope the Debian Python Applications Packaging Team will consider > packaging it... Dear Debian Python Applications Packaging Team, will you consider packaging the new version, please? Please let me know, thanks for your time. Bye. -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpweQPM4i9h1.pgp Description: PGP signature
Bug#818107: The future of DocOnce
On Mon, 7 Nov 2016 17:03:07 + Kristian Gregorius Hustad wrote: > Version 1.0.0 is now listed at https://github.com/hplgit/doconce/releases That's awesome, thanks a lot! :-) Now I hope the Debian Python Applications Packaging Team will consider packaging it... -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpnKW5npr0Y6.pgp Description: PGP signature
Bug#818107: The future of DocOnce
On Sun, 30 Oct 2016 00:03:20 + Kristian Gregorius Hustad wrote: > Hello, Hi Kristian, thanks a lot for your prompt reply. > > I think the main reason why the Debian packages haven't been kept > up to date is in part that the list of dependencies have become very > large and complex. Some of the dependencies are installed from PIP > or even cloned from git (the full list can be found at > https://github.com/hplgit/doconce/blob/master/doc/src/manual/debpkg_doconce.txt). I was being silent, since I was hoping to see some comments from the Debian Python Applications Packaging Team. I cannot really say anything meaningful about the number or the complexity of the dependencies, as I am not familiar with the packaging details of the doconce Debian package. I hope someone from the Debian Python Applications Packaging Team will express his/her opinion about this. [...] > I have thought about having a release branch and tagging releases, > but I haven't gotten around to do it yet. Please, please, begin tagging releases, so that https://github.com/hplgit/doconce/releases will include something. I think this would make it clearer to the downstream distributions (such as Debian) when there's a new release to be packaged. > > I hope to be able to find the time to maintain DocOnce, but I'm afraid > I won't be able to develop it at the same pace as HPL. Even though the addition of new features may get slower, it would still be awesome, if you could begin taking care of reported bugs and basic software maintenance for DocOnce. > Hopefully, there will be more contributors in the future. Sure. And making DocOnce more "downstream-friendly" (the first step would be to clearly identify releases, as already discussed) could help in increasing the user base, which often leads to more chances to find some new contributor!;-) Bye and thanks for your helpfulness. -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpkeSioxUvYF.pgp Description: PGP signature
Bug#818107: The future of DocOnce
Hello, I think the main reason why the Debian packages haven't been kept up to date is in part that the list of dependencies have become very large and complex. Some of the dependencies are installed from PIP or even cloned from git (the full list can be found at https://github.com/hplgit/doconce/blob/master/doc/src/manual/debpkg_doconce.txt). Additionally, until recently, DocOnce was developed solely by its original creator, Hans Petter Langtangen (hereafter referred to as HPL), so improvements and fixes have just been released continuously to the master branch. I have thought about having a release branch and tagging releases, but I haven't gotten around to do it yet. I hope to be able to find the time to maintain DocOnce, but I'm afraid I won't be able to develop it at the same pace as HPL. Hopefully, there will be more contributors in the future. Kristian
Bug#818107: The future of DocOnce
Hello, I am a Free Software user and contributor from Italy. I became interested in DocOnce, since I think it's a very promising documentation format and system. I wanted to see a more up-to-date version of DocOnce included in Debian (my GNU/Linux distribution of choice), hence I filed a bug report against the doconce Debian package on the Debian BTS: https://bugs.debian.org/818107 It turned out that the maintainers of the doconce Debian package haven't packaged recent versions of DocOnce, because no formal releases have come out recently. I said that the developers of DocOnce should be contacted and encouraged to begin tagging (from now on) specific points of history in the git repository, so that the maintainers of the Debian package could have some defined "releases" to package. Please see the already cited full bug log for further details. In the meanwhile, I found out that the main author of DocOnce sadly passed away on October 2016, the 10th. I am very sorry for this loss... :-( I am now wondering: what's the future of DocOnce? I hope that someone is taking over its development. Maybe you? I see that you are the author the latest commit on the public git repository and you have contributed to DocOnce several times. Could you please share some news with us? Please note that I am Cc-ing the bug e-mail address. Please keep it in Cc list, when replying, so that your message gets added to the bug log and is publicly readable by all interested party. Thanks for your time and for any help you may provide! -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpwbkcgmnipq.pgp Description: PGP signature
