On Tue, Sep 22, 2009 at 5:39 AM, MJ Ray <span dir="ltr"><<a href="mailto:mjr@phonecoop.coop">mjr@phonecoop.coop</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">Joann Ransom <<a href="mailto:jransom@library.org.nz">jransom@library.org.nz</a>> wrote:<br>
> I think forming a combined 'open source in libraries' foundation is<br>
> definitely worth considering. I don't know much about Code4Lib as an<br>
> organisation, but is that a body tat may have arole to play here? I need<br>
> more information!<br>
<br>
</div>I thought code4lib was a conference, email list and website, not a<br>
non-profit corporation, so turning that into a FOSS-for-libraries<br>
association (please not a foundation) would be about the same amount<br>
of work.<br>
<br>
Sharing overheads would be good, but I wonder if the different history<br>
of Evergreen may mean the communities are too different, that we would<br>
be looking for different things. For example, conferences and<br>
extending development seem high on their list of priorities, but not<br>
near the top of our doodle straw-poll. That may just be because we've<br>
had independent conferences and new developers often already.<br>
<br>
Probably worth exploring though. Anyone willing to try leading that<br>
effort? If so, please add it to<br>
<a href="http://wiki.koha.org/doku.php?id=kohaheldbyfoundation" target="_blank">http://wiki.koha.org/doku.php?id=kohaheldbyfoundation</a><br>
in the "New FOSS Libraries association or foundation" column.<br></blockquote></div><br><br>Code4Lib members have typically resisted formalization of the community structure overall, while still supporting more defined working subunits (Conference planning, T-shirt committee, the Journal, etc.). We are likely to find allies in that group, but not a home for a Koha Foundation. <br>
<br>I think there should be some Koha association (call it "Koha Foundation", "Koha Core", "Koha Crew", "Kohaxors Intl." -- the name is unimportant to me) to serve as the more democratic and active version of what was initially conceived as the role of Kaitiaki. This seems to me the natural fit, and not overreaching. <br>
<br>If there is a joining of forces between Koha and Evergreen, I think it should be (at least at first) as a working group, at a low level. "What can we do to help each other? What code components can we share?" It is far too soon to talk about merging projects or codebases... let alone hypothetical foundational bodies.<br>
<br>It does not seem reasonable to expect the high level foundation/governance questions to be ironed out simultaneously between both communities when neither has them clarified internally. Indeed, like MJ, I suspect that neither community would much appreciate a formal governance body, in particular since it is hard to see where it would get (1) resources or (2) developers. Even if a unified body promoted both ILS's, I would still want individual groups that focused on each project, so basically, I think each community should pursue it's own group.<br>
<br>In fact, I can see broader FOSS4LIB type group forming and being active (over more than these 2 projects) more quickly and more effectively than a Koha/Evergreen group (over *just* those 2 projects). <br><br>--Joe Atzberger<br>