[Building Sakai] RSF Present and Future

Steven Githens swgithen at mtu.edu
Fri Feb 5 13:57:06 PST 2010


I sort of have mixed feelings about this.  At the moment, while 
maintaining existing Sakai code, I typically end up fixing a couple bugs 
a year in RSF or it's related libraries, and I don't *really* want to 
fix them in 2 places.  It seems like it would make pretty good sense to 
fork SakaiRSF, but I'm not sure about the 3 core RSF/Servlet/Ponder jars.

I guess I'm somewhat impartial, but would we fork a floating apache 
project?  ( like James ( or log4j/velocity if they died or something else ))

I'm pretty lazy, so at the moment it seems like more work to fork these, 
but I guess it might make sense in the future. ( or if we were using a 
version control system like git or hg that could import all the history 
of them ( I don't know maybe a new version of subversion let's you do 
this across repositories now? ) )

-s

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



More information about the sakai-dev mailing list