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

[May, Megan Marie]

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<mailto: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/78294b9e/attachment.html