[sakai2-tcc] Agenda - Re: Invitations sent for TCC - CLECC meeting this week

Tue Dec 11 20:00:55 PST 2012

I would agree with this,

However most of the tools in Sakai are such bad shape that it would
probably be faster if you (or other developers) just wrote a new tool or
integrated a new external tool rather than trying to fix what's there now.
There are no longer support teams in core except for:

Samigo - Karen
Profile2 - Steve
Assignments/Site-Manage - Zhen
Lessons - Chuck
Messages and Forums - Michelle
Portal - (Probably still Dr. Chuck and Adrian, though a little of everybody)

That's it.

If there's an issue with any other tool it's it needs to be high priority,
then it's almost always someone from that above list or one of the
commercial affiliates that looks at it.

i18n status is easy, Alan has a dashboard for that:
http://qa1-nl.sakaiproject.org/international/ . However the help files only
exist for Chinese, Portuguese and some in French and Russian. Help as has
already been discussed is a big technical problem.

Also . . .

- Both tools that extend the BaseMessageService should be replaced. Email
Archive & Announcements. There are about 100 open issues in both of those
tools that will never be looked at and multiple developers have put in
patches and left (Sakai). They're difficult to figure out and the bugs are
hard to fix when they need to be fixed. There might be some great technical
idea to improve the storage of all the XML content then selectively pulling
out data that needs to be indexed over time (in fact I know there is, using
new tables instead of columns to index this schema-less data). However
implementing that could take more time than using something new. . . Though
maybe neither of these tools or any of the 100 issues are that really that
important.

- Even though Assignment has someone working on it, it should either be
decided to keep Assignment forever or replace it with Assignments 2. There
are pros and cons for both which I was planning on writing up in a future
message. Technical cleanup in both Assignment and site-manage seems to be
an ongoing project.

- We really could use a better UI for Gradebook and the
edu-services/gradebook split seems only half completed. Many edu-service
beans are still in gradebook, so edu-services won't start without gradebook
present anyway. Also Noah recently worked on a time consuming performance
fix and he mentioned there was a lot of logic that is in gradebook tool.
This is not unique to gradebook (logic in the tool layer) and will make
writing accurate external interfaces difficult. The GB2/GB split I'm sure
has some gap because of this.
  - Speaking of GB2, it looks like GXT has added an exception for their
license since the last time we reviewed it (years ago) possibly making the
library compatible for use. Though we'd probably want someone to confirm
this.

http://www.sencha.com/legal/open-source-faq/open-source-license-exception-for-applications/
  - Though the gaps mentioned above would need to be re-addressed

- Web tool (SAK-12563) needs to be replaced with portlet version, News Tool
should be replaced with News Feeds

- It's a bummer that Content/Resources UI work wasn't finished by Michigan.
That tool could really use some HTML5 improvements. Still too difficult to
deal with files.

- Ideally Postem, Site Stats, Polls, Podcasts and Syllabus are in decent
shape and not too many issues. Syllabus probably isn't as useful with
Lessons. Post'em I've done some minor work in lately.

- RWiki . . . A wiki is super important but this really needs to be
removed/replaced. Nobody is touching it, it's using a 5 year old library
(Radeox) that I'd bet only Sakai is using, every large attempt (WYSIWYG) to
seriously improve it has failed. (SAK-8535)
  - I don't even know what to do with this . . .  It has almost 100 open
issues by itself.

These are all new things that weren't on the 2.10 hit list (
https://confluence.sakaiproject.org/display/TCC/TCC+CLE+2.9+Action+Items) ,
but since you were talking about maintainable tools. That hit-list still
needs a review, perhaps a meeting to go over this stuff?

On Tue, Dec 11, 2012 at 10:06 PM, Steve Swinsburg <steve.swinsburg at gmail.com
> wrote:
>
> I see a lot of value in ensuring that the current modules we have are
> maintainable, still meet licensing requirements, have an identified support
> team, are internationalised, and many other aspects, mostly technical.
> There is a lot of amazingly crap and over complex code in various modules
> that, whilst it still works, is a pain point for anyone making a
> modification or extension, and if someone had some time could have some
> love to make it better. That could be identified from the review.
>
> We are also talking about periodic review of projects to ensure they still
> meet the criteria.
>
> cheers,
> S
>
>
> On Wed, Dec 12, 2012 at 10:10 AM, Anthony Whyte <arwhyte at umich.edu> wrote:
>
>> Equating CLE modules with fully-fledged projects in the JA-SIG mold
>> would, in many cases, be inappropriate.  Given this, generating separate
>> checklists for each in a manner similar to or inspired by the JA-SIG
>> incubation process is not much of a value add in my view. [1]
>>
>> Anth
>>
>> [1] https://wiki.jasig.org/display/INCU/Incubation+Process
>>
>>
>> On Dec 11, 2012, at 5:38 PM, Steve Swinsburg wrote:
>>
>> Yes, could be a lot of work, however I think its important that all
>> modules meet the criteria for the new Foundation and we don't have code
>> slipping in that has never been reviewed. It should just be a checklist
>> that can be walked though. At least then we know the state of each.
>>
>>
>> On Wed, Dec 12, 2012 at 9:26 AM, May, Megan Marie <mmmay at indiana.edu>wrote:
>>
>>>  All modules?   That sounds like quite the effort****
>>>
>>> ** **
>>>
>>> *From:* sakai2-tcc-bounces at collab.sakaiproject.org [mailto:
>>> sakai2-tcc-bounces at collab.sakaiproject.org] *On Behalf Of *Steve
>>> Swinsburg
>>> *Sent:* Tuesday, December 11, 2012 5:19 PM
>>> *To:* Seth Theriault
>>> *Cc:* sakai2-tcc at collab.sakaiproject.org 2
>>> *Subject:* Re: [sakai2-tcc] Agenda - Re: Invitations sent for TCC -
>>> CLECC meeting this week****
>>>
>>> ** **
>>>
>>> RE incubation, the Apereo board is working through a document about how
>>> we think incubation might work and what its goals are. We should have more
>>> to report soon. ****
>>>
>>> ** **
>>>
>>> In any case, yes, there will be an incubation process, how it relates to
>>> the CLE and other existing projects is being discussed. My initial thoughts
>>> are for a review of all modules of CLE for code debt, areas for
>>> enhancements and maintenance/support, rather than just grandfathering it
>>> all in.****
>>>
>>> ** **
>>>
>>> On Wed, Dec 12, 2012 at 8:13 AM, Seth Theriault <slt at columbia.edu>
>>> wrote:****
>>>
>>> On Tue, Dec 11, 2012 at 4:06 PM, Neal Caidin
>>> <nealcaidin at sakaifoundation.org> wrote:
>>>
>>> > We may not cover all this, but here is a brain dump of things that need
>>> > attention.****
>>>
>>> [...]****
>>>
>>> > - Transition to Apereo - nothing to report at the moment , but
>>> something
>>> > that should be on the radar screen. I'm getting a new Apereo email
>>> address
>>> > soon.****
>>>
>>> I may not make tomorrow's meeting, so here's a comment. In theory,
>>> there is supposed to be a "lightweight" incubation process for the CLE
>>> and the other Jasig/Sakai top-level projects. I am pretty sure the
>>> existing Jasig Incubation group was spearheading this, but there seem
>>> to be few details about this that have been publicly communicated
>>> apart from the meeting notes:
>>>
>>> https://wiki.jasig.org/display/INCU/Meetings
>>>
>>> If anyone out there has more info (Steve S.?), I'd love to hear it.
>>>
>>> Seth
>>> _______________________________________________
>>> sakai2-tcc mailing list
>>> sakai2-tcc at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc****
>>>
>>> ** **
>>>
>>
>> _______________________________________________
>> sakai2-tcc mailing list
>> sakai2-tcc at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>>
>>
>>
>
> _______________________________________________
> 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/20121211/a8c1bf4f/attachment-0001.html 