[Building Sakai] RSF Present and Future

[Jim Eng]

+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.

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"
>
>