[sakai2-tcc] TCC - CLECC summary - June 13, 2013

Anthony Whyte arwhyte at umich.edu
Fri Jun 14 06:40:05 PDT 2013


On the subject of 2.9.4, I thought our San Diego conversation had trended away from a Nov/Dec 2.9.4 maintenance release in favor of focusing on 2.10 alpha/beta work and that a proposal would be crafted along those lines?  I question whether we have the capacity to do both and maintain a reasonable level of quality as regards output.

> Some of the ideas which have been discussed include (but not finalized) - Dashboard, Project Keitai, Updated LTI, Common Cartridge Export (Lessons), Elastic Search, TinCan API (Learning Analytics), Many potential Samigo improvements, new Online Help (this is currently still in requirements phase, no set timeline), perhaps the Signup Tool


A number of the above listed improvements are already in trunk.  Do we really want to hold back on Keitei, TinCanAPi, LTI 2.0, Lessons improvements et al by diverting energy away from trunk in favor of a fourth 2.9 maintenance release?  One could I suppose cherry pick certain of these improvements and back port them to 2.9.x but that could prove messy plus it would violate our current practice of restricting *.x branch enhancements to those of the minor variety.

There is also the desire to root out the indies and simplify our build/release practices--the focus of this work will be on trunk not 2.9.x.

I suggest that the idea of 2.9.4 be held in reserve and only exercised if unforeseen 2.9.x blockers bubble to the surface post-2.9.3.  Note, that the "stuff" of 2.10--or whatever folks want to version the next major/minor release--is far more compelling that what a 2.9.4 can hope to deliver. 

Cheers,

Anth       




On Jun 13, 2013, at 11:06 PM, Neal Caidin wrote:

> Next meeting - Tuesday, June 25, 1 pm Eastern Daylight / 5 pm GMT   (alternating between East coast morning for 2nd week and afternoon for 4th week seems to be best balance of TCC attendee availability)
> 
> * CLA update (Licensing/Audit) - Neal plans to work with Anthony W. in early July. Some Apereo-level discussion also happening in parallel.
> 
> * Post Sakai CLE 2.9.2 items? Have updated all Jira projects to have appropriate release versions/release dates/fix versions. 2.9.3-related version numbers were added a few weeks back. Some cleanup work may still be needed, but the main tasks are done (including SiteStats).
> 
> * Background for 2.9.3 and 2.10 discussion - TCC discussions in San Diego - https://confluence.sakaiproject.org/display/TCC/2013+Apereo+TCC+Meeting+Notes
> 
> * Discussion only. CLE 2.9.3 
>       - release in July (earlier the better) to provide schools an opportunity to use for August/September school term.
>       - AntiSamy on by default? Sam O. initiated that discussion already. 
>       - Minimal release - maybe a few Kernel issues, Security issues and others. 
>       - Update of online help information being discussed (Perl script does not include new help documents or deleting help documents, only updates)
>       - other Jiras, like translations, could also potentially get into the release, if fixed and verified in time, but would not hold up the release?
>       - probably a proposal coming soon to TCC since we need a fast decision to line things up. 
> 
> * Discussion only. CLE 2.9.4
>      - tentatively plan for a "meatier" 2.9.4 for the October timeframe so that schools could implement for a January 2014 release?
> 
> * Discussion only. CLE 2.10
>       - What would it take to have a beta by November? Or is it really more of an alpha?
>       - Need a good story/significant content to justify a 2.10 release over a 2.9.x update.  Some of the ideas which have been discussed include (but not finalized) - Dashboard, Project Keitai, Updated LTI, Common Cartridge Export (Lessons), Elastic Search, TinCan API (Learning Analytics), Many potential Samigo improvements, new Online Help (this is currently still in requirements phase, no set timeline), perhaps the Signup Tool
>       - mid-September through mid-November might be an ideal time to capture contributions from the Community (after the semester start)
>       - Should we have each potential major project assigned to a TCC member to monitor? Chase down some work from schools likely to contribute (Indiana, UMich, Stanford, Yale, Virginia, Cape Town, etc) ? 
>      
> * Documentation cleanup from Confluence to a more controlled approach - Neal will get information on Apereo web redesign efforts to coordinate with effort being led by Seth (see details at https://confluence.sakaiproject.org/pages/viewpage.action?pageId=83036135 and sample structure at http://etherpad.ctools.org/sakai-docs) .  Need to get a better handle on time frames for these efforts and ownership of content/site etc.
> 
> * Still need date for completing Tools survey summary for community (received more data recently). Starting to think about a community outreach survey. Neal will discuss with TCC Chair/Vice Chair
> 
> * Open Apereo 2013 - some feedback that technical infrastructure was not reliable (e.g. internet speed). Conference committee aware of this and addressing. A survey will be sent out soon.
> 
> Cheers,
> 
> Neal Caidin
> 
> Sakai CLE Community Coordinator
> nealcaidin at sakaifoundation.org
> Skype: nealkdin
> AIM: ncaidin at aol.com
> 
> 
> 
> 
> 
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20130614/a2f3fd1e/attachment-0001.html 


More information about the sakai2-tcc mailing list