[OPEN-ILS-DOCUMENTATION] Launchpad instance

[Ben Shum]

I'm -1 to a separate Launchpad instance if only because Evergreen's 
documentation has been and is continuing to be merged into the master 
code of Evergreen now.  So to me, we should be tracking documentation 
issues in the same place we track other aspects of Evergreen's code so 
that developers, etc. are mindful of documentation-related efforts 
alongside their own.

We have been using tagging to keep track of "documentation" bugs, and 
there are some links (like 
https://bugs.launchpad.net/evergreen/+bugs?field.tag=documentation) that 
people can use to get those bugs listed out.  That said, I can see how 
it might be helpful for people who focus only on documentation to 
receive notifications only for documentation bugs based on signing up to 
a dedicated tracker.  That'll keep them sane instead of having to sift 
through however many normal bug announcements are published from Launchpad.

So I guess I'm actually closer to 0 (neutral) on this proposal.

-- Ben

On 09/05/2012 12:57 PM, Peters, Michael wrote:
>
> I'd be willing to go +1 on a separate instance, if it's not too much 
> trouble to host and people are familiar with administrating it.  I 
> think it's good to keep things separate.  Seeing all of the software 
> bugs could certainly be overwhelming if you're only looking to help 
> with documentation.
>
> Sincerely,
> Michael Peters
> Indiana State Library MIS | Inspire.IN.gov Helpdesk | Evergreen 
> Indiana Helpdesk
> office - 317.234.2128
> email - mrpeters at library.in.gov <mailto:mrpeters at library.in.gov>
>
> *From:*open-ils-documentation-bounces at list.georgialibraries.org 
> [mailto:open-ils-documentation-bounces at list.georgialibraries.org] *On 
> Behalf Of *Duimovich, George
> *Sent:* Wednesday, September 05, 2012 12:28 PM
> *To:* open-ils-documentation at list.georgialibraries.org
> *Subject:* [OPEN-ILS-DOCUMENTATION] Launchpad instance
>
> 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
> OPEN-ILS-DOCUMENTATION at list.georgialibraries.org
> http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation

-- 
Benjamin Shum
Open Source Software Coordinator
Bibliomation, Inc.
32 Crest Road
Middlebury, CT 06762
203-577-4070, ext. 113

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.georgialibraries.org/pipermail/open-ils-documentation/attachments/20120905/7456df1a/attachment-0001.htm>