[sakai-pmc] [Building Sakai] Sign up proposal for Sakai 10
Neal Caidin
neal.caidin at apereo.org
Mon Dec 30 11:57:03 PST 2013
I haven't heard any objections, so I believe that the Sign Up tool is
approved for Sakai 10?
Hopefully there is enough time to get it in before the Apereo Camp in
late January :-)
Cheers,
Neal
> Liu, Peter <mailto:peter.liu at yale.edu>
> December 20, 2013 at 12:34 PM
>
> There are two new features introduced into trunk:
>
> 1)Site import/archive functionality
>
> 2)Timezone conversion (according to user's preference setting)
>
> We are testing them at Yale currently and they will be ready and
> deployed into our production on January, 8, 2014.
>
> Thanks,
>
> Peter
>
> *From:*sakai-dev-bounces at collab.sakaiproject.org
> [mailto:sakai-dev-bounces at collab.sakaiproject.org] *On Behalf Of *Neal
> Caidin
> *Sent:* Friday, December 20, 2013 8:51 AM
> *To:* Charles Severance; sakai-pmc at collab.sakaiproject.org;
> sakai-dev at collab.sakaiproject.org
> *Cc:* Rinaldi, Louis; Hirsch, David;
> cle-release-team at collab.sakaiproject.org
> *Subject:* Re: [Building Sakai] [sakai-pmc] Sign up proposal for Sakai 10
>
> Two things that came up on the Sakai release team meeting yesterday .
> A couple of new features have been added to the Signup Tool recently
> and haven't been tested in production. Therefore they will need
> special attention in QA testing. One is archiving. I didn't catch what
> the other features are.
>
> The other item, which I mentioned actually, is that the Accessibility
> team anticipates a lot of work if this tool is added. I'm not sure of
> the specifics, but it sounds the Sign up tool is probably in good
> shape for internationalization and security, but maybe not so much for
> accessibility.
>
> We discussed the possibility of adding the tool as provisional/stealthed.
>
> Thanks,
> Neal
>
>
>
>
>
>
>
> *Charles Severance* <mailto:csev at umich.edu>
>
> December 19, 2013 at 9:48 PM
>
> Megan,
>
> I will echo Matt's comments. While I am not ecstatic about JSF or
> RSF, if a tool has been running for a long time using JSF, it would be
> a mistake to try a switch its UI framework just because we are moving
> it to core The very reason we would consider promoting something is
> that it is stable, reliable and running in production lots of places
> (i.e. boring).
>
> Honestly, if we were to request a rewrite, it might be a year before
> we could agree on the right UI framework to use :) I like Portlets
> that use Velocity or JSP but I know there are many other opinions :)
>
> For better or worse, we are stuck with JSF and RSF for a long time - a
> little more or less hardly matters.
>
> /Chuck
>
> *May, Megan Marie* <mailto:mmmay at iu.edu>
>
> December 18, 2013 at 4:14 PM
>
> I've been watching the list to see if anyone was going to weigh in.
> Still waiting J
>
> If we as a community are ok with JSF as a supported technology, I'll
> remove my objection (ie -1). I've heard it used as a reason to
> remove tools or as an argument to refactor tools so I'd like to see us
> have a clear position on this.
>
> Megan
>
> *From:*sakai-pmc-bounces at collab.sakaiproject.org
> <mailto:sakai-pmc-bounces at collab.sakaiproject.org>
> [mailto:sakai-pmc-bounces at collab.sakaiproject.org] *On Behalf Of *Neal
> Caidin
> *Sent:* Wednesday, December 18, 2013 8:52 AM
> *To:* Steve Swinsburg; sakai-pmc at collab.sakaiproject.org
> <mailto:sakai-pmc at collab.sakaiproject.org>;
> sakai-dev at collab.sakaiproject.org
> <mailto:sakai-dev at collab.sakaiproject.org>
> *Cc:* Rinaldi, Louis; Hirsch, David
> *Subject:* Re: [sakai-pmc] [Building Sakai] Sign up proposal for Sakai 10
>
> Does anybody else have the JSF concern that Megan raised ?
>
> It sounds like the discussion about incubation is a separate thread
> and if Yale wishes to go through that process it can be made to work
> for Sakai 10?
>
> Therefore, please provide any final comments, concerns and blockers
> within the next couple of days, by Friday, December 20.
>
> Let's try and wrap all these proposals up, one way or another. :-)
>
> Thanks,
> Neal
>
>
>
>
> *Steve Swinsburg* <mailto:steve.swinsburg at gmail.com>
>
> December 16, 2013 at 6:14 PM
>
> Conversely, if a tool developer wishes to progress through incubation,
> as Peter has indicated, I see no reason to object to that. The
> incubation process is designed to assist developers in ensuring that
> licensing, accessibility and internationalisation is squared away,
> that builds are standardised, that the development and support model
> is sustainable and to answer any questions. This is not an intrusive
> process. The developers get one on one assistance and at the end the
> project will be a sponsored by Apereo.
>
>
>
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> <mailto:sakai-dev at collab.sakaiproject.org>
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org
> <mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a subject
> of "unsubscribe"
>
> *Anthony Whyte* <mailto:arwhyte at umich.edu>
>
> December 16, 2013 at 9:36 AM
>
> As in the case of skin-manager, I see no need for Signup to seek
> incubation status under Apereo. Advance the proposal under the terms
> of the lazy consensus as has been done with new tool promotions like
> roster2 and the news tool replacement.
>
> anthony whyte | its and mlibrary | university of michigan |
> arwhyte at umich.edu <mailto:arwhyte at umich.edu> | 517-980-0228
>
>
>
> _______________________________________________
> sakai-pmc mailing list
> sakai-pmc at collab.sakaiproject.org
> <mailto:sakai-pmc at collab.sakaiproject.org>
> http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
>
> *Liu, Peter* <mailto:peter.liu at yale.edu>
>
> December 16, 2013 at 9:27 AM
>
> Thanks Adam! You and your team haven been a big supporter all these
> years for Signup tool.
>
> Steve,
>
> Yale and me will definitely continue supporting the Signup tool in a
> long haul. I would be happy to submit a request to Apereo incubation
> process and need more detail about this process.
>
> Thanks a lot!
>
> Peter
>
> *From:*Adam Marshall [mailto:adam.marshall at it.ox.ac.uk]
> *Sent:* Monday, December 16, 2013 5:02 AM
> *To:* Steve Swinsburg; Liu, Peter
> *Cc:* Rinaldi, Louis; Hirsch, David; Adam Marshall; Matthew Buckett;
> Benjamin Holmes
> *Subject:* RE: [Building Sakai] Sign up proposal for Sakai 10
>
> If you need anything from Oxford then please do say.
>
> We will help you to support the tool: we will help to fix bugs where
> they are deemed to be important, help with documentation but cannot
> guarantee to add new feature requests if they don't align with our
> priorities.
>
> Hope this helps.
>
> adam
>
> *From:*sakai-dev-bounces at collab.sakaiproject.org
> <mailto:sakai-dev-bounces at collab.sakaiproject.org>
> [mailto:sakai-dev-bounces at collab.sakaiproject.org] *On Behalf Of
> *Steve Swinsburg
> *Sent:* 15 December 2013 23:02
> *To:* Liu, Peter
> *Cc:* Rinaldi, Louis; Hirsch, David; sakai-pmc at collab.sakaiproject.org
> <mailto:sakai-pmc at collab.sakaiproject.org>;
> sakai-dev at collab.sakaiproject.org
> <mailto:sakai-dev at collab.sakaiproject.org>
> *Subject:* Re: [Building Sakai] Sign up proposal for Sakai 10
>
> Peter, would you be open to submitting this tool through the Apereo
> incubation process?
> http://www.apereo.org/content/incubation
>
> That way we can ensure everything is in order.
>
> Whilst I have worked on the tool considerably thanks to various
> initiatives, and it is an extremely useful tool with some decent
> integrations and features, a promotion to core is not a drop off point
> for code to be maintained by others, as the core team of committers
> are stretched as it is. If Yale was committed to its support for a
> while, that would be ideal.
>
> cheers,
> Steve
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> <mailto:sakai-dev at collab.sakaiproject.org>
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org
> <mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a subject
> of "unsubscribe"
>
> *Steve Swinsburg* <mailto:steve.swinsburg at gmail.com>
>
> December 15, 2013 at 6:02 PM
>
> Peter, would you be open to submitting this tool through the Apereo
> incubation process?
> http://www.apereo.org/content/incubation
>
> That way we can ensure everything is in order.
>
> Whilst I have worked on the tool considerably thanks to various
> initiatives, and it is an extremely useful tool with some decent
> integrations and features, a promotion to core is not a drop off point
> for code to be maintained by others, as the core team of committers
> are stretched as it is. If Yale was committed to its support for a
> while, that would be ideal.
>
> cheers,
> Steve
>
>
>
>
> _______________________________________________
> sakai-pmc mailing list
> sakai-pmc at collab.sakaiproject.org
> <mailto:sakai-pmc at collab.sakaiproject.org>
> http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
>
> *Liu, Peter* <mailto:peter.liu at yale.edu>
>
> December 13, 2013 at 2:56 PM
>
> Proposal: Promote Sign-Up tool to Core status for Sakai 10
>
> Rationale:
>
> The Yale Sign-up tool^[1] <#_ftn1> was initially introduced to the
> Sakai community at a BOF during the Dec. 2007 Sakai Conference in
> Newport^[2] <#_ftn2> after several months' consultation with partner
> schools on shared functional requirements.^[3] <#_ftn3> Sign-up was
> first offered as a contrib tool in 2008, and has since been broadly
> adopted by the worldwide community. Although we don't have data on the
> exact number of downloads, schools deploying the tool include
> Michigan, Indiana, Stanford, Yale, UNISA, Virginia, Texas, Florida,
> Oxford, Cambridge, UC Berkeley, Australian National, Charles Sturt,
> and Columbia. We also know that Asahi Net clients are actively using
> the tool.
>
> In last spring's 2013 Sakai Tool Survey^[4] <#_ftn4>, the Sign-up tool
> was the most actively used contrib tool, showing more than twice as
> much significant use (45% of the 70 schools polled) as all other
> contrib tools apart from Gradebook2 (35%).
>
> At Yale we have very limited resources to contribute to open-source
> community initiatives. The sole programmer for Sign-up, Peter Liu,
> finds it increasingly difficult to keep up with the community's
> requests for feature additions as the community grows larger. Peter
> will continue to support maintenance and development of the tool
> however he can, and has recently put in considerable effort to add two
> new functions necessary for core inclusion (time zone conversion and
> "import from site"). But rather than risk being unable to maintain the
> foregoing level of tool support as usage increases, we hope that
> promotion of the tool to core will ensure its continued viability as a
> supported tool for the entire community.
>
> There is a growing programming community around the Sign-up tool, with
> Oxford, Michigan and rSmart contributing components of the code and
> supporting documentation in recent years. Key Sakai partners such as
> Steve Swinsburg have offered assistance in promoting the tool to core.
>
> The tool follows Sakai CLE standards for localization and
> internationalization (we know of three English versions: American,
> British, Australian, and one Spanish version of the tool). We are not
> aware of any security vulnerabilities. The tool has not yet been fully
> tested for accessibility compliance.
>
> We are in the process of getting the Apereo licensing agreement signed
> so that this promotion can be considered. Our local Sakai project lead
> (David Hirsch) has received verbal confirmation from Yale's Director
> of Technology Licensing that they have no objections to signing the
> standard Apereo CCLA.
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> <mailto:sakai-dev at collab.sakaiproject.org>
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org
> <mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a subject
> of "unsubscribe"
>
> --
> Neal Caidin
> Sakai Community Coordinator
> Apereo Foundation
> neal.caidin at apereo.org <mailto:neal.caidin at apereo.org>
> Skype me! (but let me know in advance for the first interaction) -
> nealkdin
>
> *Neal Caidin* <mailto:neal.caidin at apereo.org>
>
> December 18, 2013 at 8:52 AM
>
> Does anybody else have the JSF concern that Megan raised ?
>
> It sounds like the discussion about incubation is a separate thread
> and if Yale wishes to go through that process it can be made to work
> for Sakai 10?
>
> Therefore, please provide any final comments, concerns and blockers
> within the next couple of days, by Friday, December 20.
>
> Let's try and wrap all these proposals up, one way or another. :-)
>
> Thanks,
> Neal
>
>
> *Steve Swinsburg* <mailto:steve.swinsburg at gmail.com>
>
> December 16, 2013 at 6:14 PM
>
> Conversely, if a tool developer wishes to progress through incubation,
> as Peter has indicated, I see no reason to object to that. The
> incubation process is designed to assist developers in ensuring that
> licensing, accessibility and internationalisation is squared away,
> that builds are standardised, that the development and support model
> is sustainable and to answer any questions. This is not an intrusive
> process. The developers get one on one assistance and at the end the
> project will be a sponsored by Apereo.
>
>
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> <mailto:sakai-dev at collab.sakaiproject.org>
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org
> <mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a subject
> of "unsubscribe"
>
> *Anthony Whyte* <mailto:arwhyte at umich.edu>
>
> December 16, 2013 at 9:36 AM
>
> As in the case of skin-manager, I see no need for Signup to seek
> incubation status under Apereo. Advance the proposal under the terms
> of the lazy consensus as has been done with new tool promotions like
> roster2 and the news tool replacement.
>
> anthony whyte | its and mlibrary | university of michigan |
> arwhyte at umich.edu <mailto:arwhyte at umich.edu> | 517-980-0228
>
>
> _______________________________________________
> sakai-pmc mailing list
> sakai-pmc at collab.sakaiproject.org
> <mailto:sakai-pmc at collab.sakaiproject.org>
> http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
>
> --
> Neal Caidin
> Sakai Community Coordinator
> Apereo Foundation
> neal.caidin at apereo.org <mailto:neal.caidin at apereo.org>
> Skype me! (but let me know in advance for the first interaction) -
> nealkdin
>
> Neal Caidin <mailto:neal.caidin at apereo.org>
> December 20, 2013 at 8:51 AM
> Two things that came up on the Sakai release team meeting yesterday .
> A couple of new features have been added to the Signup Tool recently
> and haven't been tested in production. Therefore they will need
> special attention in QA testing. One is archiving. I didn't catch what
> the other features are.
>
> The other item, which I mentioned actually, is that the Accessibility
> team anticipates a lot of work if this tool is added. I'm not sure of
> the specifics, but it sounds the Sign up tool is probably in good
> shape for internationalization and security, but maybe not so much for
> accessibility.
>
> We discussed the possibility of adding the tool as provisional/stealthed.
>
> Thanks,
> Neal
>
>
>
>
>
>
>
> Charles Severance <mailto:csev at umich.edu>
> December 19, 2013 at 9:48 PM
> Megan,
>
> I will echo Matt's comments. While I am not ecstatic about JSF or
> RSF, if a tool has been running for a long time using JSF, it would be
> a mistake to try a switch its UI framework just because we are moving
> it to core The very reason we would consider promoting something is
> that it is stable, reliable and running in production lots of places
> (i.e. boring).
>
> Honestly, if we were to request a rewrite, it might be a year before
> we could agree on the right UI framework to use :) I like Portlets
> that use Velocity or JSP but I know there are many other opinions :)
>
> For better or worse, we are stuck with JSF and RSF for a long time - a
> little more or less hardly matters.
>
> /Chuck
>
>
>
> May, Megan Marie <mailto:mmmay at iu.edu>
> December 18, 2013 at 4:14 PM
>
> I've been watching the list to see if anyone was going to weigh in.
> Still waiting J
>
> If we as a community are ok with JSF as a supported technology, I'll
> remove my objection (ie -1). I've heard it used as a reason to
> remove tools or as an argument to refactor tools so I'd like to see us
> have a clear position on this.
>
> Megan
>
> *From:*sakai-pmc-bounces at collab.sakaiproject.org
> [mailto:sakai-pmc-bounces at collab.sakaiproject.org] *On Behalf Of *Neal
> Caidin
> *Sent:* Wednesday, December 18, 2013 8:52 AM
> *To:* Steve Swinsburg; sakai-pmc at collab.sakaiproject.org;
> sakai-dev at collab.sakaiproject.org
> *Cc:* Rinaldi, Louis; Hirsch, David
> *Subject:* Re: [sakai-pmc] [Building Sakai] Sign up proposal for Sakai 10
>
> Does anybody else have the JSF concern that Megan raised ?
>
> It sounds like the discussion about incubation is a separate thread
> and if Yale wishes to go through that process it can be made to work
> for Sakai 10?
>
> Therefore, please provide any final comments, concerns and blockers
> within the next couple of days, by Friday, December 20.
>
> Let's try and wrap all these proposals up, one way or another. :-)
>
> Thanks,
> Neal
>
>
>
> *Steve Swinsburg* <mailto:steve.swinsburg at gmail.com>
>
> December 16, 2013 at 6:14 PM
>
> Conversely, if a tool developer wishes to progress through incubation,
> as Peter has indicated, I see no reason to object to that. The
> incubation process is designed to assist developers in ensuring that
> licensing, accessibility and internationalisation is squared away,
> that builds are standardised, that the development and support model
> is sustainable and to answer any questions. This is not an intrusive
> process. The developers get one on one assistance and at the end the
> project will be a sponsored by Apereo.
>
>
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> <mailto:sakai-dev at collab.sakaiproject.org>
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org
> <mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a subject
> of "unsubscribe"
>
> *Anthony Whyte* <mailto:arwhyte at umich.edu>
>
> December 16, 2013 at 9:36 AM
>
> As in the case of skin-manager, I see no need for Signup to seek
> incubation status under Apereo. Advance the proposal under the terms
> of the lazy consensus as has been done with new tool promotions like
> roster2 and the news tool replacement.
>
> anthony whyte | its and mlibrary | university of michigan |
> arwhyte at umich.edu <mailto:arwhyte at umich.edu> | 517-980-0228
>
>
> _______________________________________________
> sakai-pmc mailing list
> sakai-pmc at collab.sakaiproject.org
> <mailto:sakai-pmc at collab.sakaiproject.org>
> http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
>
> *Liu, Peter* <mailto:peter.liu at yale.edu>
>
> December 16, 2013 at 9:27 AM
>
> Thanks Adam! You and your team haven been a big supporter all these
> years for Signup tool.
>
> Steve,
>
> Yale and me will definitely continue supporting the Signup tool in a
> long haul. I would be happy to submit a request to Apereo incubation
> process and need more detail about this process.
>
> Thanks a lot!
>
> Peter
>
> *From:*Adam Marshall [mailto:adam.marshall at it.ox.ac.uk]
> *Sent:* Monday, December 16, 2013 5:02 AM
> *To:* Steve Swinsburg; Liu, Peter
> *Cc:* Rinaldi, Louis; Hirsch, David; Adam Marshall; Matthew Buckett;
> Benjamin Holmes
> *Subject:* RE: [Building Sakai] Sign up proposal for Sakai 10
>
> If you need anything from Oxford then please do say.
>
> We will help you to support the tool: we will help to fix bugs where
> they are deemed to be important, help with documentation but cannot
> guarantee to add new feature requests if they don't align with our
> priorities.
>
> Hope this helps.
>
> adam
>
> *From:*sakai-dev-bounces at collab.sakaiproject.org
> <mailto:sakai-dev-bounces at collab.sakaiproject.org>
> [mailto:sakai-dev-bounces at collab.sakaiproject.org] *On Behalf Of
> *Steve Swinsburg
> *Sent:* 15 December 2013 23:02
> *To:* Liu, Peter
> *Cc:* Rinaldi, Louis; Hirsch, David; sakai-pmc at collab.sakaiproject.org
> <mailto:sakai-pmc at collab.sakaiproject.org>;
> sakai-dev at collab.sakaiproject.org
> <mailto:sakai-dev at collab.sakaiproject.org>
> *Subject:* Re: [Building Sakai] Sign up proposal for Sakai 10
>
> Peter, would you be open to submitting this tool through the Apereo
> incubation process?
> http://www.apereo.org/content/incubation
>
> That way we can ensure everything is in order.
>
> Whilst I have worked on the tool considerably thanks to various
> initiatives, and it is an extremely useful tool with some decent
> integrations and features, a promotion to core is not a drop off point
> for code to be maintained by others, as the core team of committers
> are stretched as it is. If Yale was committed to its support for a
> while, that would be ideal.
>
> cheers,
> Steve
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> <mailto:sakai-dev at collab.sakaiproject.org>
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org
> <mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a subject
> of "unsubscribe"
>
> *Steve Swinsburg* <mailto:steve.swinsburg at gmail.com>
>
> December 15, 2013 at 6:02 PM
>
> Peter, would you be open to submitting this tool through the Apereo
> incubation process?
> http://www.apereo.org/content/incubation
>
> That way we can ensure everything is in order.
>
> Whilst I have worked on the tool considerably thanks to various
> initiatives, and it is an extremely useful tool with some decent
> integrations and features, a promotion to core is not a drop off point
> for code to be maintained by others, as the core team of committers
> are stretched as it is. If Yale was committed to its support for a
> while, that would be ideal.
>
> cheers,
> Steve
>
>
>
> _______________________________________________
> sakai-pmc mailing list
> sakai-pmc at collab.sakaiproject.org
> <mailto:sakai-pmc at collab.sakaiproject.org>
> http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
>
> *Liu, Peter* <mailto:peter.liu at yale.edu>
>
> December 13, 2013 at 2:56 PM
>
> Proposal: Promote Sign-Up tool to Core status for Sakai 10
>
> Rationale:
>
> The Yale Sign-up tool^[1] <#_ftn1> was initially introduced to the
> Sakai community at a BOF during the Dec. 2007 Sakai Conference in
> Newport^[2] <#_ftn2> after several months' consultation with partner
> schools on shared functional requirements.^[3] <#_ftn3> Sign-up was
> first offered as a contrib tool in 2008, and has since been broadly
> adopted by the worldwide community. Although we don't have data on the
> exact number of downloads, schools deploying the tool include
> Michigan, Indiana, Stanford, Yale, UNISA, Virginia, Texas, Florida,
> Oxford, Cambridge, UC Berkeley, Australian National, Charles Sturt,
> and Columbia. We also know that Asahi Net clients are actively using
> the tool.
>
> In last spring's 2013 Sakai Tool Survey^[4] <#_ftn4>, the Sign-up tool
> was the most actively used contrib tool, showing more than twice as
> much significant use (45% of the 70 schools polled) as all other
> contrib tools apart from Gradebook2 (35%).
>
> At Yale we have very limited resources to contribute to open-source
> community initiatives. The sole programmer for Sign-up, Peter Liu,
> finds it increasingly difficult to keep up with the community's
> requests for feature additions as the community grows larger. Peter
> will continue to support maintenance and development of the tool
> however he can, and has recently put in considerable effort to add two
> new functions necessary for core inclusion (time zone conversion and
> "import from site"). But rather than risk being unable to maintain the
> foregoing level of tool support as usage increases, we hope that
> promotion of the tool to core will ensure its continued viability as a
> supported tool for the entire community.
>
> There is a growing programming community around the Sign-up tool, with
> Oxford, Michigan and rSmart contributing components of the code and
> supporting documentation in recent years. Key Sakai partners such as
> Steve Swinsburg have offered assistance in promoting the tool to core.
>
> The tool follows Sakai CLE standards for localization and
> internationalization (we know of three English versions: American,
> British, Australian, and one Spanish version of the tool). We are not
> aware of any security vulnerabilities. The tool has not yet been fully
> tested for accessibility compliance.
>
> We are in the process of getting the Apereo licensing agreement signed
> so that this promotion can be considered. Our local Sakai project lead
> (David Hirsch) has received verbal confirmation from Yale's Director
> of Technology Licensing that they have no objections to signing the
> standard Apereo CCLA.
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> <mailto:sakai-dev at collab.sakaiproject.org>
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org
> <mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a subject
> of "unsubscribe"
>
> --
> Neal Caidin
> Sakai Community Coordinator
> Apereo Foundation
> neal.caidin at apereo.org <mailto:neal.caidin at apereo.org>
> Skype me! (but let me know in advance for the first interaction) -
> nealkdin
>
> Neal Caidin <mailto:neal.caidin at apereo.org>
> December 18, 2013 at 8:52 AM
> Does anybody else have the JSF concern that Megan raised ?
>
> It sounds like the discussion about incubation is a separate thread
> and if Yale wishes to go through that process it can be made to work
> for Sakai 10?
>
> Therefore, please provide any final comments, concerns and blockers
> within the next couple of days, by Friday, December 20.
>
> Let's try and wrap all these proposals up, one way or another. :-)
>
> Thanks,
> Neal
>
>
>
--
Neal Caidin
Sakai Community Coordinator
Apereo Foundation
neal.caidin at apereo.org
Skype me! (but let me know in advance for the first interaction) - nealkdin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20131230/4c44c7c4/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: compose-unknown-contact.jpg
Type: image/jpeg
Size: 770 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20131230/4c44c7c4/attachment-0008.jpg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.jpg
Type: image/jpeg
Size: 886 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20131230/4c44c7c4/attachment-0009.jpg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.jpg
Type: image/jpeg
Size: 1251 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20131230/4c44c7c4/attachment-0010.jpg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.jpg
Type: image/jpeg
Size: 992 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20131230/4c44c7c4/attachment-0011.jpg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.jpg
Type: image/jpeg
Size: 889 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20131230/4c44c7c4/attachment-0012.jpg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postbox-contact.jpg
Type: image/jpeg
Size: 1304 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20131230/4c44c7c4/attachment-0013.jpg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.jpg
Type: image/jpeg
Size: 1251 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20131230/4c44c7c4/attachment-0014.jpg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.jpg
Type: image/jpeg
Size: 992 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20131230/4c44c7c4/attachment-0015.jpg
More information about the sakai-pmc
mailing list