[sakai-pmc] Incubation questions

[Anthony Whyte]

The incubation process to which you refer makes sense for projects or communities who wish to be recognized as a top-level Apereo project or community.  [1]  Sakai modules such as roster2, the skin manager or the signup tool are not in the same category and to conflate such small "p" projects with top-level candidates is not helpful in assessing what we should be doing from a process perspective.

If we "try out" the Apereo incubation process as you suggest on proposed contrib promotions to core we will find ourselves having to draw up proposal submissions that ultimately require board approval according to the published process. [1]  Are you really proposing that we should move in that direction?  Again, the process makes sense when applying it to an external entity wishing to join Apereo; it's laying it on more than a bit thick when applied to a contrib module.

In my opinion, we are perfectly capable of handling such reviews in house.  As regards cross-cutting concerns such as licensing we as a community are tied into the appropriate Apereo structures.  In the case of both the skin manager and signup the Apereo license group has been briefed on the licensing issues raised by their nomination to core.

What I'd like to see from Steve or any other Sakai contributor is a review proposal for new Sakai capabilities that is lightweight, "right-sized" for the target capability in question, and capable of being executed by Sakai contributors without resort to the IWG, an IWG-appointed Mentor or ultimately the Sakai Board. 

Cheers,

Anth

[1] http://www.apereo.org/content/s3-core-process



anthony whyte | its and mlibrary | university of michigan | arwhyte at umich.edu | 517-980-0228


On Dec 17, 2013, at 8:59 AM, Neal Caidin wrote:

> imho, we should give the incubation process a try which will allow us to see if it does add value to the Sakai product, and if it doesn't add enough value, provide feedback to the process. This is how quality improves over time. If we never try, we'll never know. 
> 
> Now there is the question of whether this will impact features going into Sakai 10. But that is not really a conflict is it? Because we want to know what the quality of the tools are going into Sakai 10 and to ensure they are good. If a tool is not quite ready during our Sakai 10 timeline, I presume we would yank it and schedule for a later version (Sakai 10.x or Sakai 11), to give enough time to get the quality where we need it? We would do that with or without the incubation process, correct?
> 
> Thanks,
> Neal
> 
> 
> 
>> 	Bryan Holladay	December 17, 2013 at 8:53 AM
>> I was under the impression that the incubation process was for new projects: "providing scaffolding for the formation of new projects and communities of interest through their critical formative stages" [1]  Sakai has obviously been around for a long time and it's suite of tools should be vetted within Sakai's community.  I'm not discounting the incubation process and if they are willing to lend resources to vet tools, then by all means use that resource if you feel the need to (or the community suggests to before adopting).  However, it shouldn't be a requirement.  We as a community shouldn't be adopting any tools that are added to core without satisfying a certain number to "ticks" [2] such as internationalization, since that is a big feature of Sakai (internationalization that is).
>> 
>> -Bryan
>> 
>> 
>> [1] http://www.apereo.org/content/incubation
>> [2] Steve (see above, or below; depends on your email client)
>> 
>> 
>> 
>> _______________________________________________
>> sakai-pmc mailing list
>> sakai-pmc at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
>> 	Steve Swinsburg	December 17, 2013 at 5:46 AM
>> Hi J-F,
>> 
>> The Apereo incubation process has been out for a couple of months and is ramping up now with a number of projects going in. The period of consultation to develop the process was earlier in the year and concluded at the conference mid year. Have a look here for some more info:
>> http://www.apereo.org/content/incubation
>> 
>> There is a google group you can participate in to ask more questions (link on the page above).
>> 
>> cheers,
>> Steve
>> 
>> 
>> 
>> _______________________________________________
>> sakai-pmc mailing list
>> sakai-pmc at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
>> 	Jean-Francois Leveque	December 17, 2013 at 5:25 AM
>> Steve,
>> 
>> How long has the first release of incubation been available?
>> 
>> My opinion based on its pre-release was negative.
>> 
>> Hope I get time to review it again and give feedback. Is the feedback 
>> public and how is it done?
>> 
>> Thanks,
>> J-F
>> _______________________________________________
>> sakai-pmc mailing list
>> sakai-pmc at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
> 
> -- 
> Neal Caidin
> Sakai Community Coordinator
> Apereo Foundation
> neal.caidin at apereo.org
> Skype me! (but let me know in advance for the first interaction) - nealkdin
> 
> _______________________________________________
> sakai-pmc mailing list
> sakai-pmc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20131217/cf601104/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: compose-unknown-contact.jpg
Type: image/jpeg
Size: 770 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20131217/cf601104/attachment-0002.jpg 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postbox-contact.jpg
Type: image/jpeg
Size: 1251 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20131217/cf601104/attachment-0003.jpg