[Building Sakai] RSF Present and Future

[Aaron Zeckoski]

I think we should definitely maintain the RSF jars in the sakai maven
2 repo (along with all the other jars Sakai depends on), however, I
just do not see any reason to fork the RSF codebase. If Antranig is
willing to move the code into the Sakai SVN for some reason then
great, but what good is having two copies of it in different SVNs that
can get out of sync?
If there is concern about keeping the source then we should just push
src jars into the maven repo.
-1 for forking RSF

-AZ


On Fri, Feb 5, 2010 at 8:24 PM, csev <csev at umich.edu> 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"
>



-- 
Aaron Zeckoski (azeckoski (at) vt.edu)
Senior Research Engineer - CARET - University of Cambridge
https://twitter.com/azeckoski - http://www.linkedin.com/in/azeckoski
http://aaronz-sakai.blogspot.com/ - http://tinyurl.com/azprofile