[Building Sakai] Project Coordination meetings

[Clay Fenlason]

Just in case not everyone's checking the Confluence page, we'll be
starting tomorrow (Sunday) morning at 9 a.m. in Grand Mesa A, on the
2nd floor of the hotel.

~Clay

On Wed, Jun 9, 2010 at 5:52 PM, Clay Fenlason
<clay.fenlason at et.gatech.edu> wrote:
> Although travel schedules are well set by this point, one final
> reminder of the project coordination meetings [1] bookending the
> conference, including draft guidelines:
>
> * Things don't get decided at the project coordination meetings, they
> get worked up into proposals to go on-list. No one should feel that
> they have to attend a particular project coordination session in order
> to have a voice on a given topic. We just use the sessions to make
> rapid, f2f progress toward concrete proposals that include a diversity
> of perspectives. They are not the last word.
> * The sessions are meant to be working meetings that make progress
> toward some practical consensus. Debate that is not leading that
> direction may be tabled or directed elsewhere.
> * In order to keep the sessions productive, a certain baseline of
> familiarity with Sakai and its processes - the kind possessed by those
> active in Sakai development and its release processes - is assumed.
> Those new to Sakai may find it hard to follow along, and other
> sessions throughout the conference (especially the orientation
> sessions on Monday) may be more appropriate.
>
> ~Clay
>
> [1] http://confluence.sakaiproject.org//x/rgQhB
>
> On Tue, May 25, 2010 at 12:15 PM, Clay Fenlason
> <clay.fenlason at et.gatech.edu> wrote:
>> I've revised the specific goals for the Project Coordination meetings
>> [1], though I haven't heard any comment on them (consider this an
>> invitation):
>>
>> 1) To have a clear 2.8 release plan proposal (with scope, resource
>> plan, calendar, etc.) available for public comment by the end of the
>> conference
>> 2) To acquire clear institutional commitment of resource to deliver on
>> this plan (and if adequate resource cannot be recruited, to alter the
>> plan accordingly)
>> 3) To achieve (1) and (2) for a Sakai 3 project plan as well
>>
>> All of this involves a lot of pre-cooking of discussion and
>> information-gathering, which is already underway and should continue
>> through the conference.
>>
>> ~Clay
>>
>> [1] http://confluence.sakaiproject.org//x/rgQhB
>>
>