[Koha] Proposal to form Koha Technical Committee

[Lori Bowen Ayre]

Thanks for pointing out those links.  Glad there is the start of a path to
find the info.  Yet, I didn't find any guidelines for writing an RFC.
 Here's what happens:

"For Librarians" page prominently displays the link to
Add your request to our bug database <http://bugs.koha-community.org/>
 (pointing
you to Bugzilla) and then says for "detailed instruction" See this page on
our wiki for detailed instructions (which points you to)
<http://wiki.koha-community.org/wiki/Enhancement_Request_Guidelines>
http://wiki.koha-community.org/wiki/Enhancement_Request_Guidelines  which is
not about RFCs at all.  It is a confusing and scary screenshot of Bugzilla
(at first glance anyway).

The wiki page called RFCs-Koha Wiki says this much about RFCs:
"add an RFC on the wiki. Be as detailled as possible. Specify an expected
date of availability (deadline if sponsored), if it's sponsored (and if you
want, by who). Use the template RFC (see below) to fill your template"

Here's what I (as someone thinking the new feature I might want to pursue)
feel is missing (and I'm no usability expert). I a am suggesting these
specifics in hopes of being helpful, not to complain:

   - What does RFC means.
   - Is there a template or an example of a good one.
   - How to post it (the instructions do say to "send a mail on the mailing
   list but again...saying what?  attaching the RFC?  including the RFC in the
   post?  naming the Bugzilla numbers? feature names?)
   - Are there guidelines about how to name it and relate it back to a
   Bugzilla entry.  Is it one Bugzilla entry per RFC or could there be multiple
   Bugzilla entries in an RFC?

And back to the RFC Wrangler (RW?) idea, maybe the RM could select the RW
who would serve with him or her throughout the release cycle?  Just a
thought.  I do think it would be useful to have someone monitor the
enhancement request process and try to coordinate and track what people need
to ensure it funnels into the RM and development team.

Lori



On Tue, Nov 9, 2010 at 6:53 PM, Chris Nighswonger <
cnighswonger at foundations.edu> wrote:

> Hi Lori,
>
>
> On Tue, Nov 9, 2010 at 7:48 PM, Lori Bowen Ayre <lori.ayre at galecia.com>
> wrote:
> > Chris,
> > I think one of the problems is that the above-described simple
> > process/workflow is not articulated clearly anywhere.  There is a page
> > (http://koha-community.org/about/enhancing-koha/) that talks about
> varies
> > ways to use Bugzilla but no mention of RFCs and that part of the process.
> > Maybe adding a page that describes the process would help.  With some
> sample
> > RFCs.  And info on how that relates to Bugzilla.  Such a page could be
> > linked to from "For Librarians" as well as the "Get Involved" page and
> > possibly others.
>
> Actually this information is available on the wiki and is linked to from
> both the "For Librarians<http://koha-community.org/get-involved/for-librarians/>->Submitting
> your ideas (RFCs)" and the "For Developers<http://koha-community.org/get-involved/for-developers/>->RFC
> Guidelines" pages on the website. It is also linked to from the
> "Participation," "Development," and "Release Management" in the wiki. The
> direct link is: http://wiki.koha-community.org/wiki/Category:RFCs and has
> been up since back in May sometime.
>
> Kind Regards,
> Chris
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.katipo.co.nz/pipermail/koha/attachments/20101110/74ca198c/attachment-0001.htm