[sakai2-tcc] TCC - CLECC meeting this Wednesday at 10 am Eastern Daylight/ 2 pm GMT

Tue Apr 16 12:32:25 PDT 2013

A few notes for background to spur conversation. See below, interspersed with Megan's comments.

On Apr 16, 2013, at 12:30 PM, "May, Megan Marie" <mmmay at indiana.edu> wrote:

> It would be good to touch base on areas of focus for CLECC
>  
> *  Making the QA process continuous

- Not sure exactly what this means? Does this mean keep QA testing going in between release cycles?
- QA team is thinking we should get full regression testing in between cycles, because during cycles there is not sufficient time. There are only 2 or 3 active testers who regularly work on scripts.
- Here is our progress on updating full Regression scripts - http://bit.ly/ZBOICa
- Automated testing could help hugely here. How can I learn what is involved?

> * JIRA mgmt.  
- Great! Having specific goals would be helpful
- I currently do try and "pre-triage" new tickets that come in weekly (off the Longsight report for CLE release team)
- Just this past weekend successfully overcame my own stupidity and got a jira-python module to work! Gives me hope that I might be able to generate useful reports to help create a more systematic approach to this stuff. (I'm starting by semi-automating the Jira Triage process). 
- It wouldn't take me long to give an update on who is participating in Jira Triage. One of the challenges of seeing how well this is working is that some tickets get looked at but don't move from Awaiting Review/Unassigned, so hard to get good metrics. 

> * 2.9.2
What is this?  Never heard of it. (ha ha)

> * Update on security (communication, audit of CCLA’s)
- Planning on sending the update to security contacts around the same time as the 2.9.2 is released (you know, whatever that is).  It will focus on security issues fixed for 2.9.x and will mention if 2.8.x is fixed or not. Should maybe have some specific AntiSamy information/recommendations, I think.

- Audit - the first person/institution I looked for wasn't on our list in Confluence!  So I checked with this  not-on-the-list-person and they say their institution has provided these. Ian D. has pointed me to Concentra. Waiting to hear back from them to understand the process, gaps in the process, how to do an audit, etc.

> * Update on Conference planning
- CLE will be extremely well represented! I hope TCC is happy about this. 
- I have been leading an effort to include a Networking event with food, on day one (monday). I would be happy to share what we are thinking if you (TCC) want to provide input.
- I'll plan on traveling to San Diego the Thursday before. M. Jones and I have a training session for Friday. Defining our deliverables for this training and/or having some tangible goals is something we were planning on. Ideas welcome.

>  
>  
> From: sakai2-tcc-bounces at collab.sakaiproject.org [mailto:sakai2-tcc-bounces at collab.sakaiproject.org] On Behalf Of Neal Caidin
> Sent: Tuesday, April 16, 2013 11:27 AM
> To: sakai2-tcc at collab.sakaiproject.org
> Subject: Re: [sakai2-tcc] TCC - CLECC meeting this Wednesday at 10 am Eastern Daylight/ 2 pm GMT
>  
>  
> Another agenda item:
>  
> Tools Survey idea
>  
> Potential goals of a tools survey:
>  
> * Highlight tools that are available in Sakai CLE but which many in the community might not be as aware of. For example, LTI.
> * Get a sense of the impact of stealthing or removing the rWiki tool
> * Identify potential institutions or individuals who have an interest in helping maintain various tools (like rWiki, but could be other tools that need attention as well)
> * Make clear the status of the Gradebook 2 tool (my understanding is that it is built on technology with incompatible licensing with CLE?)
> * Make visible the requirements of the Assignments vs Assignments 2 tools.
> * Get a sense of the use of Contrib tools. Again with the idea that out of this might come some additional resources for development, as well as helping to identify needs
> * Get a sense of implicit, explicit or emerging requirements and needs overall
>  
> Or, as Steve Swinsburg says, maybe a simple survey will work for rWiki:
>  
> "A simple survey would do here:
> 1. Do you use the wiki (y/n)
> 2. What so you use it for (options)
> 3. If the wiki went away, how sad would you be (really sad, a bit sad, meh, I'd just use another tool, I hate the wiki)"
>  
> CLECC goal is to generate conversation and strategies for information that would be helpful input to the TCC in decision making processes wrt tool needs, and to get input from the community.
>  
>  
> On Apr 16, 2013, at 5:18 AM, Jean-Francois Leveque <jean-francois.leveque at upmc.fr> wrote:
> 
> 
> My i18n/L10n WG role and the TCC: how do we work together?
> 
> Thanks,
> J-F
> 
> On 15/04/2013 19:33, Neal Caidin wrote:
> 
> Please submit your ideas for agenda items. We will meet with or without
> an agenda since at a minimum we should check in (been about a month),
> and we are in the middle of the CLE 2.9.2 release.
> 
> 
> Calliflower
> ---------------------
> Default Dial-in Number:+1-734-418-9028
> 
> Your Conference Code: 8600146
> 
> Meeting Web Link: https://apps.calliflower.com/conf/show/455322
> 
> Find a Dial in number in your city:
> https://apps.calliflower.com/account/call_in_numbers?organizer=328940
> 
> Skype:
> 
> Add ‘calliflowerskype’ as a contact in Skype. You can then call
> Calliflower directly from Skype.
> 
> Thanks,
> 
> Neal Caidin
> 
> Sakai CLE Community Coordinator
> nealcaidin at sakaifoundation.org <mailto:nealcaidin at sakaifoundation.org>
> Skype: nealkdin
> AIM: ncaidin at aol.com <mailto: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/20130416/dfcf7444/attachment.html 