[Building Sakai] Development efforts in Incubation

[Clay Fenlason]

This communication is overdue, but I wanted to highlight projects that
have entered incubation, following the new community process shaped
earlier this year. [1]

It's worth pointing out that incubation for Sakai is not like Apache
incubation - it is more about incubating a plan to merge a portion of
work with a larger product than incubating an independent body of code
and the unique community surrounding it  - and the threshold for Sakai
incubation is a relatively low one of self-documentation. Those
projects that have moved from R&D to incubation are identified and
documented in the wiki. [2]

I'm using the word 'project' warily, because part of what may happen
in incubation is that overlapping efforts may be drawn together, and
we don't want to encourage a rigid notion of project boundary. However
I don't have a better word at the moment.

The Product Council, which has as its charge the stewardship of the
process leading from incubation to Sakai release, is working to firm
up its process and criteria iteratively. I'll be trying to communicate
results more widely, but if you're interested in following or
participating in more focused discussions I'd encourage you to join
the 'management' list. [3] For the next couple weeks the council will
be working through an exercise focussed on new Sakai 2 capabilities,
and will be doing that on-list as much as possible.

~Clay

PS If you're leading a development effort that you'd like to see enter
incubation and have questions, please feel free to post them on the
management list. [3]

[1] http://confluence.sakaiproject.org//x/sgTtAw
[2] http://confluence.sakaiproject.org//x/fgvtAw
[3] http://collab.sakaiproject.org/mailman/listinfo/management