[sakai-pmc] Outcomes of PMC - CLECC call - Thursday October 10, 2013

[Neal Caidin]

Outcomes was a poor word choice for the subject line. And, apparently, I got some of the essence wrong with #2, so I must have misunderstood. Hoping that Anthony or Seth can jump on and clarify.

Cheers,
Neal



Neal Caidin
Sakai CLE Community Coordinator
neal.caidin at apereo.org
Skype: nealkdin
Twitter: ncaidin









On Oct 10, 2013, at 6:16 PM, Steve Swinsburg <steve.swinsburg at gmail.com> wrote:

> Can we get some more info on point 2? Why was that suggested?
> 
> Project coordination and planning is the job of the PMC. Once that is decided, then maybe delegate to the release team to implement but the PMC should be providing the overall direction and guidance.
> 
> I also presume that this was a suggestion that needs to be voted upon to be all inclusive, for those that cannot or could not attend the phone call.
> 
> Thanks
> Steve
> 
> sent from mobile device
> 
> On 11/10/2013 5:23 AM, "Neal Caidin" <neal.caidin at apereo.org> wrote:
> <fluff class=trivial>	.. or should my role be called Sakai Community Coordinator? SACC?  I don't know, that sounds like an accrediting agency or something, or a sports commission (I'm in ACC-land).  You had to be there. Playing off a comment that CLE release team should be called Sakai release team.</fluff>
> 
> 1) Survey -  I got some additional feedback on the Community survey. I'm going to add a Role question and explicitly focus this survey at an individual level, not an institutional level. I'll make a final draft and provide PMC  for final review before publishing.
> 
> 2) **** IF YOU READ NOTHING ELSE - read this one *****  At the call it was suggested that the schedule and scope, and related decisions,  of the 2.10 release be pushed down to the CLE release team (aka Sakai release team).  I am going to proceed based on this input, which means, among other things, that most of the 2.10 discussion will occur on the CLE release team email list and NOT on the PMC list.  Since there is so much overlap between the lists, I'm not anticipating this causing any signficant disruption to the planning process.
> 
> 3) Scope of 2.10 - see #2
> 
> 4) Sakai Test suite - https://github.com/johntbush/sakai-test-suite - not something ready to help with 2.10 testing, perhaps could evolve into something that is picked up by the community. It sounds like a cool start though.
> 
> 
> 5) Jira Prod list - I'll see if I can sneak in more reminders to the community to please update their institutional data. Other than that, nothing else for this item.
> 
> 6) New SVN committers - PMC working on simplifying the process, I understand. Neal to be trained to back up the function of technically granting SVN privileges. Will work closely with Beth and Anthony to get trained and will check with them on individual requests.  Tangentially related to this are communications - will bring to Ian Dolphin's or Infrastructure group's attention that we need broad communication to the Apereo community to start using the licensing process and templates available at http://www.apereo.org/licensing , plus we need to make sure the Sakai process - which has changed, is well defined and communicated (it is the same as the Apereo process, but just need a few Sakai specific roles/responsibilities defined, I think), and we need a simple plan to decommission the Sakai Confluence area on licensing, get the old data (CLA's) moved to the new space, etc.
> 
> Thanks,
> Neal
> 
> 
> Neal Caidin
> Sakai CLE Community Coordinator
> neal.caidin at apereo.org
> Skype: nealkdin
> Twitter: ncaidin
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> 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/20131011/bc14b45f/attachment.html