I was browsing around Freenet's github profile this morning and ran across PyFCP (lib-pyFreenet). There were a few things that immediately jumped out to me as projects I could work on, but given their scope I figured I'd get some feedback before investing the effort.
First, I'd like to convert the documentation from epydoc to sphinx. Sphinx is much prettier by default, has a number of great themes, is not dead (Epydoc's last release was almost six years ago!), lends itself to user-documentation (not just API docs), and is supported by Read the Docs, a fantastic documentation project that has become the standard for Python projects. Secondly, the package is in actuality many different things, tied together merely by subject (Freenet) and implementation language (Python); a good half of the readme is a description of the various projects. Why should someone wanting to work with the Freenet protocol in Python need to install an IRC bot, or an XML-RPC server? A split should, of course, consist of a number of forks from the current HEAD, so as to maintain revision history for each project. (BTW, the 'requires' argument is misspelled 'requries' in the setup.py; I imagine setuptools would complain about this any time you attempt to build the package.) (BTW #2, what is the point of having separate -official and -staging repositories? Is this not the point of branches?) My apologies if this is stepping on any toes; I'm not at all familiar with the development history of Freenet or PyFCP, so I am relying upon you to point out any reasons things should stay as they are. Happy anonymity, - James -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://emu.freenetproject.org/pipermail/tech/attachments/20131114/af835777/attachment.html>
