[Building Sakai] RSF Present and Future

David Horwitz david.horwitz at uct.ac.za
Fri Feb 5 13:56:52 PST 2010


-1 quite simply I fail to see how forking the RSF project helps ensure
code quality  (and do you mean the whole of RSF or just the SakaiRSF
library?).

Seeing as we don't have adequate resources to maintain our own code,
maintaining a branch of 3rd party code doesn't help either.

D

Jim Eng wrote:
> +1, but *NOT* in kernel. Velocity and JSF should not be in kernel,  
> either.
>
> I agree with Mark about needing care (i.e. maintenance resources) to  
> make sure that tags, branches and releases be reflected in the Sakai  
> copy.nd 
>
> Jim
>
>
> On Feb 5, 2010, at 4:30 PM, Mark Norton wrote:
>
>   
>> +1, but we should still track Java RSF in case there are bug fixes or
>> (maybe) improvements.
>>
>> - Mark
>>
>> csev wrote:
>>     
>>> I think that in light of the near-shutdown of development around  
>>> the Java version of RSF below that I think that we should grab a  
>>> copy of RSF and put it in Kernel-1 and migrate all externals in the  
>>> source tree to our own copy of RSF rather than RSF from a separate  
>>> repo.
>>>
>>> I worry that as folks move further and further away from "Java RSF"  
>>> as a real project - we will simply lose track of things.
>>>
>>> If we make this change quickly while it is all fresh in our memory,  
>>> then we can benefit from having some institutional memory about RSF  
>>> as we take a copy of the code.
>>>
>>> /Chuck
>>>
>>> On Feb 2, 2010, at 7:27 PM, Antranig Basman wrote:
>>>
>>>
>>>       
>>>> I thought this would be an opportune moment to sent a note to the  
>>>> list
>>>> about the current and future status of RSF, since I know it is the
>>>> platform for a number of actively maintained tools which are being
>>>> managed by the community.
>>>>
>>>>         
>>> [snip ...]
>>> _______________________________________________
>>> sakai-dev mailing list
>>> 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 
>>>  with a subject of "unsubscribe"
>>>
>>>
>>>       
>> _______________________________________________
>> sakai-dev mailing list
>> 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 
>>  with a subject of "unsubscribe"
>>
>>
>>     
>
> _______________________________________________
> sakai-dev mailing list
> 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 with a subject of "unsubscribe"
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20100205/e55b5138/attachment.html 


More information about the sakai-dev mailing list