[cle-release-team] [sakai-pmc] Two new features for Sakai 10

[Neal Caidin]

We've had some comments on the MathJax jira [1] . Sounds like there is 
interest but that it sounds uncertain if we will have a solution in 
place before we cut Sakai 10 beta (at Apereo Camp at the end of January)?

I haven't seen any objections to the Print option for content resources 
[2], but there was a concern raised about lack of documentation of the 
feature and how that might affect adoption of it's use.

[1] - https://jira.sakaiproject.org/browse/SAK-22384

[2] - https://jira.sakaiproject.org/browse/SAK-25371


Last day for comments.

Thanks,
Neal


> Neal Caidin <mailto:neal.caidin at apereo.org>
> December 18, 2013 at 8:41 AM
> Looping in sakai-dev list.
>
> Hi Sakai-dev,
>
> see a proposal from last week (before the deadline) for two Jiras to 
> be included in Sakai 10, SAK-25371 and SAK-22384 . And some initial 
> comments on these issues.
>
> Please chime in ASAP. Would like to wrap this up this week.
>
> See below.
>
> Thanks,
> Neal
>
>
>
> Matthew Jones <mailto:matthew at longsight.com>
> December 17, 2013 at 5:02 PM
> I agree, not as big as an audience. I've already made comments on 
> these specific tickets but will just summarize them.
>
> On Thu, Dec 12, 2013 at 5:22 PM, Kirschner, Beth <bkirschn at umich.edu 
> <mailto:bkirschn at umich.edu>> wrote:
>
>     I'd like to propose 2 new features for Sakai 10:
>
>     https://jira.sakaiproject.org/browse/SAK-25371 - Add Optional
>     Print option to Resources "Action" menu. Requires minor kernel
>     change. We're currently testing this feature, which will require
>     institutions to implement a provider to make it active.
>
>
> Sounds good, just my previous comments on the ticket. It would be nice 
> if there was a brief document (confluence or README?) that has a 
> sample of how someone else could take advantage of writing a end 
> service for it. Ideally it would be an active test running somewhere 
> that QA could connect so we could avoid regression. Like how we can 
> easily test LTI functionality on appspot is pretty great 
> (http://simplelti.appspot.com/test.htm). Even if it just connects and 
> writes out some debugging information, would provide a great example.
>
>     https://jira.sakaiproject.org/browse/SAK-22384 - Add MathJax
>     (finally). Looks like Waterloo has something in production that
>     needs to be reviewed & merged back to trunk when available.
>
>
> Yea, I'm not sure about this. The patch seems incomplete (no sample 
> skins? no info about what from MathJax to install) and I'm still not 
> convinced scanning the entire DOM for TeX is a always good. I for sure 
> would need to be constrained to this skin but would be better if it 
> just scanned specific divs. Mathjax can do this but the user would 
> have to know what class id's to put in (either through a simple plugin 
> that would wrap it or some other docs? I wonder how much of a demand 
> there is now for that anymore with fMath included in 2.9 and many 
> places still using Wiris? The only people who'd be writing plain TeX 
> are Math/Engineering professors, and they can paste that into the 
> fMath editor and get out an image. I wouldn't be against it as long as 
> it didn't require that full 30MB+ MathJax package to run. Maybe some 
> more details about the what's required.
>
>
>
> Anthony Whyte <mailto:arwhyte at umich.edu>
> December 17, 2013 at 4:33 PM
> Yup, proposals such as this should be vetted on the sakai-dev list.
>
> anthony whyte | its and mlibrary | university of michigan | 
> arwhyte at umich.edu <mailto:arwhyte at umich.edu> | 517-980-0228
>
>
>
>
> Neal Caidin <mailto:neal.caidin at apereo.org>
> December 17, 2013 at 3:29 PM
> Hi,
>
> I haven't seen any comments on this proposal yet. Also, I notice that 
> sakai-dev has not been copied. I presume that we should copy in 
> sakai-dev list and put an ending date for comments?
>
> FWIW, SAK-25371 seems like it would be a nice function and would be 
> okay with me if it is okay with the folks who know the kernel code 
> well. Also seems like this is a manageable thing to QA test.
>
> I don't know much about MathJax but it seems like math and science 
> folks would love to have Latex support built-in to the editor. This 
> doesn't seem like a really big change to Sakai from a technical 
> perspective?
>
> Thanks,
> Neal
>
>
>
> Kirschner, Beth <mailto:bkirschn at umich.edu>
> December 12, 2013 at 5:22 PM
> I'd like to propose 2 new features for Sakai 10:
>
> https://jira.sakaiproject.org/browse/SAK-25371 - Add Optional Print 
> option to Resources "Action" menu. Requires minor kernel change. We're 
> currently testing this feature, which will require institutions to 
> implement a provider to make it active.
>
> https://jira.sakaiproject.org/browse/SAK-22384 - Add MathJax 
> (finally). Looks like Waterloo has something in production that needs 
> to be reviewed & merged back to trunk when available.
>
> - Beth
>
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team

-- 
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/cle-release-team/attachments/20131220/a71aec6f/attachment.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/cle-release-team/attachments/20131220/a71aec6f/attachment.jpg 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postbox-contact.jpg
Type: image/jpeg
Size: 1222 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20131220/a71aec6f/attachment-0001.jpg