[sakai-pmc] Feedback requested - Sakai 10 features list

Fri Dec 6 13:24:28 PST 2013

I agree, those are good points.

Hopefully the fact that we’ve been having this discussion about setting a deadline over the last couple of months or so on the public list has made most folks aware that a deadline was coming up very soon, so they are not completely unprepared. Also hopefully, since the proposal process is fairly lightweight it will make it not be too onerous even though there is not much time left. Would be good to get feedback from the community. I haven’t heard any complaints so far, which is a good thing at least. If others hear of complaints or grumblings please let me know.

I may ask Anthony and Seth (Chair / Vice Chair) for advice on my “Change Request Process” idea. The idea is that we know change happens, things come up during a release cycle,  let’s make sure the community is educated on how we handle those requests. A Change process describes how will manage the scope and schedule after we have settled on these things. From my experience so far, we have a very lightweight process for Schedule changes, they just happen (missed milestones, resource constraints due to local issues, etc), but we are more rigorous with Scope changes. I wonder if everyone agrees with that perspective.

Cheers,
Neal

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

On Dec 6, 2013, at 3:24 PM, May, Megan Marie <mmmay at iu.edu> wrote:

> Comments inline below.
>     
>  
> From: Neal Caidin [mailto:nealcaidin at sakaifoundation.org] On Behalf Of Neal Caidin
> Sent: Friday, December 06, 2013 2:11 PM
> To: May, Megan Marie
> Cc: sakai-pmc at collab.sakaiproject.org
> Subject: Re: [sakai-pmc] Feedback requested - Sakai 10 features list
>  
> Hi Megan,
>  
> A better wording for item b is 
>  
> b) Yale Signup tool - if a proposal is submitted and approved, on or off by default ? 
>  
> And perhaps we should have whether it is on or off be part of whatever proposal is made.
>  
> MMM – gotcha . . . this helps clarify a lot.   The way it was worded before made me think that a decision had already been made and this was just “paperwork.”     And yes, the proposal should prob include whether or not its on or not.   Fwiw, my understanding is this is a JSF tool which many of my peers on the PMC have indicated is a less than ideal technology.   I’d like to hear why that shouldn’t be a show stopper.
>  
> I sent a proposal out yesterday for the Sakai 10 schedule to sakai-dev and sakai-pmc [1]. Does that not qualify as being circulated ? 
>  
> MMM – that would qualify as circulated.  It’s just that it’s a short timeline and the deadline is 1 day over a week.     It just doesn’t give a lot of time for comment – particularly for proposals that haven’t been sent yet.
>  
> We had schedules floating around from discussions, and this is an attempt to firm things up. That’s why we’ve extended the date for proposals to December 13. Previous discussions, which also were on the sakai-dev list, had the date as December 6.  
>  
> What I’m trying to accomplish is to tie off loose ends so that there is clarity around what is in scope for Sakai 10 and what is not in scope.
>  
> MMM – understood.  Just want to be sure that everyone is given the opportunity to present proposals and understands there will be an enforced deadline.
>  
> [1] http://collab.sakaiproject.org/pipermail/sakai-dev/2013-December/025409.html
> 
> Thanks,
> Neal
> 
> Neal Caidin
> Sakai Community Coordinator
> neal.caidin at apereo.org
> Skype: nealkdin
> Twitter: ncaidin
> 
> 
> 
> 
> 
> 
> 
> 
>  
> On Dec 6, 2013, at 1:47 PM, May, Megan Marie <mmmay at iu.edu> wrote:
> 
> 
> Neal,
>      I’m not following what this list is trying to accomplish.  For instance look at item b.   You indicate it needs a proposal but that there are plans to have it in the code.   How can those two things happen at the same time?    And then there is the schedule . . . . which hasn’t really been circulated but has a cutoff date of the 13th.  
>  
> Megan     
>  
> From: sakai-pmc-bounces at collab.sakaiproject.org [mailto:sakai-pmc-bounces at collab.sakaiproject.org] On Behalf Of Neal Caidin
> Sent: Friday, December 06, 2013 1:36 PM
> To: sakai-pmc at collab.sakaiproject.org
> Subject: [sakai-pmc] Feedback requested - Sakai 10 features list
>  
> Hi PMC,
>  
> Okay, so this is my take on the status of the Sakai 10 features which might need a proposal [1], which are separate from other features we’ve discussed to get into Sakai 10 [2], which I think mostly don’t need proposals?
>  
>  
> a) PASSED - Link tool - decommission proposal - passed. - http://collab.sakaiproject.org/pipermail/sakai-dev/2013-October/024844.html
> b) NEEDS PROPOSAL - Yale Signup tool - plan to have it in code (on or off by default?)
> c) PASSED WITH item “g” - Roster 2 tool to replace Roster and retire Profile - http://collab.sakaiproject.org/pipermail/sakai-dev/2013-November/025226.html
> d) STATUS? - Spring Annotations - AZ . 
> e) LIMBO - Portal chat on by default - UMich had performance issues? No way to turn off during Tests? Previously decided that it would not be on?  Jira - 
> Review Portal chat performance: https://jira.sakaiproject.org/browse/SAK-22286
> Remove chat from some sites/tools: https://jira.sakaiproject.org/browse/SAK-23258
> f) PASSED with Steve’s proposal - News feed tool to replace the News tool?  or Steve Swinsburg offered his portlet as a replacement - https://wiki.jasig.org/display/PLT/Simple+RSS+Portlet - http://collab.sakaiproject.org/pipermail/sakai-dev/2013-November/025229.html
> g) PASSED WITH item “c” - Retire Profile for Profile 2 - is Profile already retired?  See item "c" above.
> h) PASSED - Retiring the old ArchiveServiceImpl - http://collab.sakaiproject.org/pipermail/sakai-dev/2013-December/025376.html
>  
> So here are my questions:
>  
> 1) Is there any sort of official announcement that should go out that says “THIS PASSED” ?  Seems like there should be that final feedback loop to the community, and that we should post to Confluence. Sound right? I am happy to help administratively but not necessarily something I should initiate. Does that make sense? Hope I am not splitting hairs, just wanting to avoid stepping on each other’s toes.
>  
> 2) There was some discussion about Spring Annotations, but not sure whether it can count for a proposal? If so, I think it passed.  [3]
>  
> 3) Portal Chat turning on by default seems like it needs a proposal and to address some concerns that were raised [4]  . So I’m thinking that one is in kind of Limbo (which would mean it would not be turned on by default. There were performance concerns and security (test-taking etc) concerns.
>  
> FYI - I’ve been in touch with the Yale folks. Sounds like we should be getting a proposal from them soon (though they still have some licensing issues to clean up, which probably will be a dependency for getting the tool into core Sakai, I’m guessing). 
>  
>  
> [1] - List of potential “big” features for Sakai 10 - https://confluence.sakaiproject.org/display/REL/Sakai+10+Release+Schedule+and+Scope
> [2] - A separate list of potential features (mostly “small”)  -  https://jira.sakaiproject.org/browse/SAK-24197
> [3] - Spring Annotations discussion - http://collab.sakaiproject.org/pipermail/sakai2-tcc/2013-September/003934.html
> [4] - Some portal chat discussion - http://collab.sakaiproject.org/pipermail/sakai2-tcc/2013-September/003932.html
>  
>  
> Cheers,
> Neal
> 
> 
> Neal Caidin
> Sakai Community Coordinator
> neal.caidin at apereo.org
> Skype: nealkdin
> Twitter: ncaidin
> 
> 
> 
> 
> 
> 
> 
> 
> 
>  
>  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20131206/9794a948/attachment-0001.html 