[OPEN-ILS-GENERAL] Evergreen Community IRC meeting reminder: Tuesday, Nov. 23 @ 2:00 PM Eastern

[Dan Scott]

(Apologies for cross-posting)

Time for another community IRC meeting, an opportunity to coordinate
efforts in real-time between all of the groups working to improve the
Evergreen project! The next Evergreen community IRC meeting will be
held at:

 * 11:00:00 a.m. Tuesday November 23, 2010 in America/Los_Angeles

 * 02:00:00 p.m. Tuesday November 23, 2010 in Canada/Eastern

 * 07:00:00 p.m. Tuesday November 23, 2010 in UTC

This is a public meeting for the Evergreen community that will be held
on the #evergreen channel on the Freenode IRC network
(http://evergreen-ils.org/irc.php). All members of the community with
an interest in contributing to the improvement of Evergreen are
welcome to participate.  If you are unable to attend at the designated
time, please feel free to submit comments for any of the agenda items
in advance to the Evergreen general mailing list.

The agenda is evolving at
http://evergreen-ils.org/dokuwiki/doku.php?id=community:meetings:2010-11
- please extend and amend to ensure that it meets the immediate
concerns of the project. At the moment the agenda is _very_ rough:
currently it is largely comprised of just status updates from the
various known groups in the community:

  - (* min) Review action items from last meeting (**No minutes!**
[[http://evergreen-ils.org/irc_logs/evergreen/2010-10/%23evergreen.19-Tue-2010.log|IRC
logs]])
  - (* min) Communications committee
  - (* min) Website Team report and discussion
  - (* min) Conference committee
  - (* min) Documentation Interest Group report
  - (* min) Developer report
  - (* min) Reports Taskforce report
  - (* min) Governance Committee report
  - (* min) Schedule next meeting

For agenda items that have the potential to be too long to express
during a single IRC meeting, it would probably make sense to post more
considered opinions in advance on this mailing list. Examples of such
agenda items might include major release process changes or
drastically revising our bug tracking processes. If a given discussion
item starts eating up too much meeting time and a decision is not
immediately necessary, we can also delegate the responsibility to a
volunteer sub-team for investigating alternatives and coming up with a
proposal for adoption at the next meeting.