Hi Shaun,
> How much maintenance burden is there for the general infrastructure of
> library-web, versus the burden of the various converters and such that
> we'd have to deal with anyway if plugging them into another system?
There's not much maintenance required, for example new modules are
automatically picked up from the jhbuild modulesets, as well as new
versions of known modules published on ftp.gnome.org.
There are a few outstanding bugs (old development versions are pruned
from the index files but not from the server, and are getting indexed by
Google), and nobody to look at them regularly (I have been doing most of
library-web work during hackfests), maybe because it's difficult to hack
on, but mostly (imho) because there are very few persons working on
infrastructure, documentation, or both.
> RTD has been hugely popular in the Python world, but it's not the only
> continuous deployment or automated docs build system out there. Red Hat
> and Fedora use Publican for almost everything. OpenStack has a big pile
> of Maven code that builds its site. There are plenty of other examples
> that I could dig up.
Indeed; as I wrote earlier I'd prefer to have ideas on the structure we
want before we go looking for the appropriate software (or changes to
the library-web code base).
Fred
_______________________________________________
desktop-devel-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
