[sakai2-tcc] Evolution of tools

Wed Nov 17 05:11:37 PST 2010

It makes little sense at this juncture in my opinion.  A call for a vote on this is premature especially as the proposal is multi-faceted in nature--add a reputed "drop in" tool or tools with modest production track records into a maintenance release and by doing so repeal our "fixes only" rule for maintenance branches.  

More particularly, if clog or blogwow is used in an attempt to pry open maintenance branches for new stuff I'll wager now that the vote will fail and no override will succeed.  Adding new tools to existing maintenance branches is of a different order than adding a new capability to an existing tool or service in maintenance mode.

I write the above only with respect to initiating a vote on the question (or questions actually).  There are a constellation of issues here embedded in the suggestion that require careful scrutiny.  We should discuss the implications of these ideas carefully.  If there is interest, we might consider setting up a sub-committee to explore the general question of opening up maintenance branches to "new" additions.  A subset of members could explore the question and report back to the whole for further consideration.

As for documentation, create a ticket that requests documentation on how to add clog and/or blogwow to 2.8.  I would not include unsupported and deprecated tools like blog in any documentation write up for 2.8 other than to make clear why we removed them.

Cheers,

Anth

On Nov 17, 2010, at 2:42 AM, Berg, Alan wrote:

> Doesn't it make sense to have a vote on having a Blog drop in for 2.8.1 and the second place well documented in the release notes. Should I Jira as a task for Blog documentation in the 2.8 release notes?
> 
> Note: I will be happy to review and report back during any QA quiet time between 2.8 and 2.8.1. 
> 
> Alan
> 
> Alan Berg
> QA Director - The Sakai Foundation
> 
> Senior Developer / Quality Assurance
> Group Education and Research Services
> Central Computer Services
> University of Amsterdam
> 
> http://home.uva.nl/a.m.berg
> From: sakai2-tcc-bounces at collab.sakaiproject.org [sakai2-tcc-bounces at collab.sakaiproject.org] on behalf of Steve Swinsburg [steve.swinsburg at gmail.com]
> Sent: 17 November 2010 08:37
> To: sakai2-tcc at collab.sakaiproject.org Coordination Committee
> Subject: Re: [sakai2-tcc] Evolution of tools
> 
> True, although clog is identical to the current blog so will be the most familiar drop in replacement. And this isn't the first time this discussion has come up, it was first proposed after the 2008 conference when the tool was Wicket based (unfortunately it was "sakai-wicket" rather than normal Wicket, which had it's own challenges). Then again earlier this year/late last year in the form of Clog.
> 
> I know that Adrian has been working hard on Clog, including making it an indie release as well as a data conversion from the old backend to the new one. But if BlogWow is a candidate for inclusion then they should both be reviewed on their merits.
> 
> I think it is unfortunate that tools are pulled from the release without a suitable replacement.
> 
> cheers,
> S
> 
> 
> 
> On 17/11/2010, at 5:44 PM, David Horwitz wrote:
> 
>> I'd like to inject some caution here - someone saying "we need a blog" does not mean that clog or blogwow will meet their needs. Remember both blog and blogWow where written to meet different use cases, both of which are in use in the community. Choosing one or the other (as we have learnt) is not going to necessarily satisfy the people who say "Sakai must have a blog"
>> 
>> D
>> 
>> On 11/17/2010 12:58 AM, Steve Swinsburg wrote:
>>> 
>>> We should bring Adrian Fish into this conversation and see where Clog [1] is up to, as it is the third iteration of the same Blog tool. The first iteration is the current blog tool, the second iteration was used in production at Lancaster for a couple of years and was Wicket based, the third is a version of the same written in HTML/Trimpath. In all cases, the UI is the same but somewhat enhanced, but the backend was made much more robust.
>>> 
>>> It is the third that I would like to see as a replacement as a blog tool is a valuable selling point for Sakai.
>>> 
>>> cheers,
>>> Steve
>>> 
>>> [1] http://confluence.sakaiproject.org/display/CLOG/Home
>>> 
>>> 
>>> On 16/11/2010, at 10:00 PM, Berg, Alan wrote:
>>> 
>>>> Hi TCC,
>>>> 
>>>> I confirm that Blogger is removed from 2.8. alpha3 webapps directory.  However, judging by recent feedback at the Spanish National Sakai congress, end-users are still looking forward to using this functionality. What should be in the release document and are there going to be any plans to foster the improvement of a replacement? The same questions for the mailtool? 
>>>> 
>>>> This brings me onto a second question. To speed up the evolution of 2.x can we consider adding improved tools to 2.8.1 and change are world view on what is a maintenance branch.
>>>> 
>>>> Alan
>>>> 
>>>> Alan Berg
>>>> QA Director - The Sakai Foundation
>>>> 
>>>> Senior Developer / Quality Assurance
>>>> Group Education and Research Services
>>>> Central Computer Services
>>>> University of Amsterdam
>>>> 
>>>> http://home.uva.nl/a.m.berg
>>>> _______________________________________________
>>>> 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
> 
> _______________________________________________
> 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/20101117/2498a06d/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3829 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20101117/2498a06d/attachment-0001.bin 