[sakai-pmc] Incubation questions

Steve Swinsburg steve.swinsburg at gmail.com
Tue Dec 17 15:20:02 PST 2013


Forgot a link in that post.
This is the list of portlets (may be a bit out of date) that have
graduated, are incubating, or are unsponsored contributions:
https://wiki.jasig.org/display/PLT/Home


On Wed, Dec 18, 2013 at 10:12 AM, Steve Swinsburg <steve.swinsburg at gmail.com
> wrote:

>
> On Wed, Dec 18, 2013 at 9:21 AM, Anthony Whyte <arwhyte at umich.edu> wrote:
>
>> 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.
>>
>
> Both can be accommodated. For instance, all portlets bundled with uPortal
> have been through incubation so that all of the checks can be done before
> they are accepted. Portlets == Sakai tools/modules.
>
>
>> In my opinion, we are perfectly capable of handling such reviews in
>> house.
>>
>
> I agree, this can be done in house. But with lazy consensus on a proposal
> for a promotion from contrib to core, if no one looks at it and checks
> things like licensing (including licensing on all dependencies),
> internationalisation, accessiblity, viability of the UI framework,
> information about installation/configuration, support going forward etc,
> then things will slip in that we don't want. I'm just about to go and
> review some of the recent proposals to make sure the basics are there.
>
>
>> 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.
>>
>
> Sure, and what I have always referred to in the lightweight process is a
> checklist to ensure everything is in order. I have mentioned the old tool
> scorecard many times before:
> https://confluence.sakaiproject.org/display/SCORE/Tool+Status+Requirements
>
> I don't think it would take much to create a page on the PMC confluence
> space that collects the requirements we are interested in. In doing so, we
> can borrow some ideas from the old Jasig process (see the checklist style
> items at Section 3):
> https://wiki.jasig.org/display/INCU/Incubation+Process
>
> Would PMC people be open to that? I would be happy to lead the development
> of the checklist that people can use.
>
> cheers,
> Steve
>
>
>
>
>> 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 <holladay at longsight.com>
>>  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 <steve.swinsburg at gmail.com>
>>  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 <jean-francois.leveque at upmc.fr>
>>  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
>>
>>
>>
>> _______________________________________________
>> 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/20131218/97b7b7e1/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 1251 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20131218/97b7b7e1/attachment-0002.jpe 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 770 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20131218/97b7b7e1/attachment-0003.jpe 


More information about the sakai-pmc mailing list