This may have been already discussed, but I've noticed that launchpad has been occasionally used for website / documentation issues & gaps, in particular, with release or install documentation "bugs" and so on.
I wonder if a *separate* launchpad instance could be effectively used by documentation group (say https://launchpad.net/evergreen-docs) for the general docs effort associated with docs.evergreen-ils.org ?. The current listserv and intermingling selected doc bugs with code bugs on launchpad may be working well enough, but I'm just wondering if a separate instance might help give better focus towards streaming tickets towards areas that are formally being looked after, as well as helping to identify gaps in documentation currently not well "owned" or edited by anyone, etc. A separate instance would still allow coders and documentation contributors to link to each other but maybe there's other advantages to a separate instance too, such as allowing developers to browse specific tickets related to their work? This could be especially useful for areas where organized effort is lacking but for which we could benefit by aggregating tickets/bugs/wishlists into task bundles for eventual one-shot efforts, or for volunteers acting as content editors for specific sections etc. So maybe we don't have a formal editor for this or that docs content, but a bundle of outstanding tickets organized / tagged for specific documentation area(s) could help a new volunteer (or vendor effort), as well as to help identify content areas lacking any sustained oversight. Or maybe launchpad or other ticketing system may be too much effort for the current size of the docs community? George George Duimovich NRCan Library / Bibliothèque de RNCan
_______________________________________________ OPEN-ILS-DOCUMENTATION mailing list [email protected] http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation
