[Evergreen-web-team] Fwd: [Eg-oversight-board] Communication guidelines: suggestion

[Lori Bowen Ayre]

June,

Check out this suggestion from Dan about communication guidelines.


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=
Lori Bowen Ayre //
Library Technology Consultant / The Galecia Group
Oversight Board & Communications Committee / Evergreen
(707) 763-6869 // Lori.Ayre at galecia.com

<Lori.Ayre at galecia.com>Specializing in open source ILS solutions, RFID,
filtering,
workflow optimization, and materials handling
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=



---------- Forwarded message ----------
From: Dan Scott <dan at coffeecode.net>
Date: Tue, Oct 11, 2011 at 1:59 PM
Subject: [Eg-oversight-board] Communication guidelines: suggestion
To: eg-oversight-board <eg-oversight-board at list.evergreen-ils.org>


Hi folks:

This is primarily for Michele and Lori, but for anyone working on the
communication guideline action items from the last meeting, I'd
strongly recommend starting with something like
http://www.theopensourceway.org/ (a respectable approach to the
subject from the people behind Red Hat and Fedora) as the basis of
whatever recommendations we come up with for Evergreen. Maybe
summarize, provide the current specific ways that we do things in
Evergreen, and link to pertinent sections of that publication for
context?

Follow-up comment from Dan:

Cool! Note that in many cases an "implementation needed" marker is in
place (they want a Red Hat / Fedora focus, I believe).

http://producingoss.com/ is a much more comprehensive take on the same
subject, and has a great chapter on communication at
http://producingoss.com/en/communications.html that we could lean on
heavily :)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-web-team/attachments/20111027/4fbe02ad/attachment.html>