[Building Sakai] [Using Sakai] [Management] Comments on the proposed dev model

[May, Megan Marie]

Anthony suggested I post this a little wider :  )


From: Michael Korcuska [mailto:mkorcuska at gmail.com] On Behalf Of Michael Korcuska
Sent: Thursday, April 02, 2009 9:19 AM
To: May, Megan Marie
Cc: management at collab.sakaiproject.org
Subject: Re: [Management] Comments on the proposed dev model

Thanks, Megan.  I'm glad you're getting the conversation started.  A few comments within:
On Apr 2, 2009, at 13:10, May, Megan Marie wrote:


Hi everyone,
   I wrote a blog entry that had some thoughts on the proposed development process.    Since not everyone follows planet sakai I  wanted to be sure to specifically share my comments with the community via a community communication channels.   There hasn't been as much on list communication as I expected so hopefully this sparks some discussion or persuades others to share their thoughts.

All the best,
Megan



URL: http://meganmariemay.blogspot.com/2009/03/proposed-sakai-development-model.html

Last Wednesday I had the opportunity to attend a webinar session given by Michael Korcuska, the Sakai Foundation Executive Director, on the proposed development model for Sakai. First, I want to say that even though there were some hiccups (gotta have them!), this was one of the most beneficial forums for communication and engagement that I've experienced in Sakai in a long time.

One of the things I liked about the proposal was that Sakai as a product is defined. I think a lack of vision has been a major hurdle these past few years. I see this a positive step forward but the devil is in the details. Before I dive into critique, I want to be clear that I don't think these are things that can't be worked through. They just happen to be points that need careful consideration and detail before we all drink the kool aid.

To begin with, the largest hurdle is going to be communication. Let's all be honest, we're all really bad at this for a multitude of reasons! The proposal adds complexity and without clear definition of who is to do what and how we're going to end up less coordinated. In addition, I have a few simple requests: I want it [communication] to be consistent, reliable and simple. Please, please don't make me read lengthy messages where I need to analyze every word for hidden meaning.

Also, I feel *strongly* that the product council should not include members of the board. The board should be visionary and assist in laying out a broad strategy for community execution (like the current proposal!). Once those members become bogged down in the day to day operational details, they will become less effective as the visionary leaders they have been elected to be. This isn't to say that there aren't members that wouldn't be a good fit on the council - they should just be one or the other.

MK: I disagree with this. I think we should take talent wherever it comes from at this point it time.  Now it may be that, eventually, the product council is where certain board members would rather spend their time (as opposed to Foundation governance issues). And I could see it eventually being a problem to have someone playing both roles.  But for now I think it would be a mistake to exclude qualified individuals.

Are we having trouble getting the names of folks and/or folks with enough time?    If that the case, I find it concerning that there aren't enough folks willing to do this job.      On a side note,  I wish these nominations were made public - I don't see why we can't collectively know who the community seeks  to represent them.


Lastly, it seems that the product council is not only tasked with being the gatekeepers and shepherds but also the group that defines the standards. Performing as gatekeepers and shepherds requires quite a different skill set and temperament than defining the standards. I'd advocate that a short term task force that was charged with initially defining said standards that the council could use. I think that approach could result in a much faster implementation of this process as well as garner a wider breadth of knowledge. Something that will be *key* in ensuring we have appropriate standards/criteria. Future looking, when the standards/criteria need revisiting, the council could recommend the community assemble a new task force.

MK:  I like this proposal very much. Are you proposing someone (the board, me?) create such a task force or that a group of willing volunteers start working on it?  I prefer the latter--community action is still the bread and butter of Sakai and is what will make this work.

I'd like for you and the board to endorse the formation of a task force.  Appoint someone to lead the group and ask for volunteers in the community that can dedicate time to it right now.

Michael


_______________________________________________
management mailing list
management at collab.sakaiproject.org<mailto:management at collab.sakaiproject.org>
http://collab.sakaiproject.org/mailman/listinfo/management

TO UNSUBSCRIBE: send email to management-unsubscribe at collab.sakaiproject.org<mailto:management-unsubscribe at collab.sakaiproject.org> with a subject of "unsubscribe"

--
Michael Korcuska
Executive Director, Sakai Foundation
mkorcuska at sakaifoundation.org<mailto:mkorcuska at sakaifoundation.org>
phone: +1 510-931-6559
mobile (US): +1 510-599-2586
skype: mkorcuska



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20090402/039e7c35/attachment-0002.html 
-------------- next part --------------
_______________________________________________
sakai-user mailing list
sakai-user at collab.sakaiproject.org
http://collab.sakaiproject.org/mailman/listinfo/sakai-user

TO UNSUBSCRIBE: send email to sakai-user-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"