[OPEN-ILS-DEV] bringing more developers into the fold

[Lori Bowen Ayre]

Thanks Ben and Dan,

FYI, the first time I asked for developer feedback to the document (in
September), I specifically inquired about both issues you raise here.  And,
in fact, I asked for your blessing to reorganize some of the content on the
site to that it was a bit more easy to follow (thus potentially eliminating
the need for a separate document).

I'll repeat those questions again now that I've got your attention!  ;)

I agree that having a document living outside of the wiki/website is not a
good idea but I didn't feel comfortable making changes to these pages on my
own.

Here's what I sent out before:

Hi All,

I've been looking over the EG website to pull together resources that would
help new developers get involved.  In doing so, I've found a lot of overlap
and perhaps a couple things that need to be updated.

Would anyone object to moving the "Contributing Code" section of this page:
 http://evergreen-ils.org/dokuwiki/doku.php?id=contributing

to this page:
http://evergreen-ils.org/dokuwiki/doku.php?id=dev:contributing_code

And of course, we should link the "contributing" page to to
"contributing_code" page.

Also, on the
http://evergreen-ils.org/dokuwiki/doku.php?id=dev:contributing_code page
there are references to Java Script and the OPAC code that I think may be
out of date given the change to Template Toolkit. Could someone update that
or tell me how it should be changed to be more accurate?

Also, on this page:
http://evergreen-ils.org/dokuwiki/doku.php?id=dev:summer_of_coding_ideas,
are there any projects listed here that are now completed or in the works?
 I'd like to share this list with potential developers as part of my
attempt to enlist new developers in our project.

Also, I think this list of core committers might be out of date.  Shouldn't
Tom Brz. from MVLc be on the list here:
http://evergreen-ils.org/dokuwiki/doku.php?id=contributing:contributors?

I'm working on a document that I can pass around to Perl programmers and
others interested in getting involved with Evergreen. When I get answers to
the above questions, I'll be happy to make the changes on the wiki (if I
can) as well as my document which I'll then share for others.

Lori


On Tue, Nov 1, 2011 at 9:02 AM, Dan Scott <dan at coffeecode.net> wrote:

> On Tue, Nov 01, 2011 at 10:22:32AM -0400, Ben Shum wrote:
> > Hi Lori,
> >
> > Overall read pretty well to me.  One tidbit I saw was that the list
> > of core committers on page 2 did not include Thomas Berenzansky from
> > Merrimac Valley Library Consortium.  His name is on the wiki page
> > equivalent:
> > http://open-ils.org/dokuwiki/doku.php?id=contributing:contributors
>
> Yes, this is a general problem with duplication of content outside of a
> content authoring system. Similarly, if the processes change it's out of
> our hands for getting those changes pushed into this dev intro document
> (which maybe needs to exist in the official documentation instead)?
>
> > Another question I had, and this is more for the developers involved
> > (Jason, Dan, and Galen), but regarding the Google Summer of Code
> > content and ideas... since this was a special project during the
> > summer of 2011 (which is past now?), is there continued commitment
> > from the original mentors for each of the specified ideas and
>
> Good point. I personally can't commit to mentoring anything at any
> random point in time; my commitment was to mentoring a project during
> the summer of 2011. I would like to be able to participate next summer,
> but can't guarantee that, and I certainly can't commit to anything right
> away.
>
> > proposals listed?  Otherwise, both the wiki page
> http://evergreen-ils.org/dokuwiki/doku.php?id=dev:summer_of_coding_ideas
> > and this document ought to be altered slightly to reflect the
> > differences.  Alternatively, the wiki page does not seem to
>
> Yes, in my opinion at least, the page should be altered accordingly.
>
> > specifically mention the Google Summer of Code project anymore, but
> > is more vague in its wording "summer of coding project ideas".
> > Perhaps aiming for a more generic "Community Coding Project Ideas"
> > might be best?
>
> Sounds good to me. Idea being that these are ideas that have been raised
> and vetted (at some level) by the Evergreen developer community as being
> valuable & feasible with an appropriate level of scope for a particular
> time & level of developer.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20111101/c036fa3e/attachment.htm>