> On Apr 28, 2017, at 8:42 AM, Christoph Reiter <reiter.christ...@gmail.com> > wrote: > > On Fri, Apr 28, 2017 at 4:11 PM, John Ralls <jra...@ceridwen.us> wrote: >> This doesn't make sense. > > I'll try to clarify. > > At least I consider the documentation and documentation generation to > be a part of the PyGObject "project" since it's hard to use without > and by "official" I meant that users, when finding the page, can > assume that it is managed by the same people as PyGObject. It might > not be visible by default, but I've added Simon and Garrett as admins > to the organization. And regarding the bus factor my thinking was that > in case I no longer care about the documentation they have admin > rights to those repos. I sadly can't move the api docs repo because > github pages does not support http redirects and all links would > break. > > Regarding the readthedocs documentation: I personally don't like wikis > for documentation as it doesn't allow for discussion about changes and > tends to accumulate lots of irrelevant and outdated infos. And since > having two different sites for the same project is confusing and I > consider the readthedocs one better now I've redirected it. Feedback > welcome. > > The reason I added Pycairo to the orga was that with multiple users > having access and PyGObject being one of few users of the Pycairo C > API there is a smaller chance that it gets unmaintained again in the > future. Another reason is that I was hoping that it would convince > people to take the fork seriously since there have been multiple fork > attempts over the last 6 years where pycairo has been unmaintained.
Christoph, Thanks, that's a much better explanation, though it still doesn't explain why you chose to host the docs and doc generator on Github instead of git.gnome.org. Likewise, while I agree with you about documentation on wikis, Gnome has http://library.gnome.org which has long hosted our API documentation. What does readthedocs.io provide that library.gnome.org doesn't? Users are far likelier to be confident that documentation is part of a Gnome project when those docs are hosted with the rest of the Gnome documentation. PyCairo is a separate issue and I can easily imagine that there are political reasons that the cairographics folks might object to a cleaner solution like letting you take over maintenance of the "official" repo or having a fork directly in Gnome. Regards, John Ralls _______________________________________________ python-hackers-list mailing list python-hackers-list@gnome.org https://mail.gnome.org/mailman/listinfo/python-hackers-list
