[Building Sakai] RSF Present and Future

[Jim Eng]

What about Aaron's suggestion? Every time there is a new release of  
RSF, three new jars get pushed into sakai's maven repo -- the  
executables, the source, and the javadocs.  Then suppose there comes a  
time when there are no new releases for several years and the RSF  
server at fluid disappears.  If somebody needed to make a change from  
source, could they do it from the source jar?

Jim



On Feb 5, 2010, at 9:49 PM, csev wrote:

> This topic always ends in a hung jury :)
>
> The -1 folks have great reasons until some Cambridge IT person stops  
> backing up the server or asks around and says "are we using this old  
> server" - and since no one in earshot says how important the server  
> is, they shut it off and send it to property disposition and then we  
> have *no source code at all*.
>
> I am not concerned about next week or next year - I am concerned  
> about five years from now.
>
> There is no comparison between this and an apache project - of  
> course we would never fork Apache - but RSF @ Cambridge is dead.   
> And over time folks will simply start to forget about it.   For now  
> we know where the source is so I say we get a copy while the getting  
> is good.   In five years - we will have the jars in our repo but not  
> even have a single clue as to how to regenerate the jars.
>
> This is like Y3K - we do what is lowest effort for the moment  
> knowing full well that by the time this becomes a problem - we will  
> no longer be around and so we simply won't care that it all falls  
> apart.
>
> /Chuck
>
>
>
> _______________________________________________
> 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"
>
>