[AG-DEV] Sourceforge set up

[Thomas D Uram]

We (Argonne) administer the old sourceforge account so can continue to use it. Also, I think it be very useful to retain the old history; we can svndump the existing repo soon. The repo is currently unavailable, but I'm sure it'll be back up within a couple days.

Tom



Am May 23, 2012 um 9:01 PM schrieb Andrew Danson <Andrew.Danson at newcastle.edu.au>:

> Hi Guys,
> 
> I've been investigating what we need to do to get the sourceforge project set up, and so far it looks pretty easy.
> Every person who needs to be a project administrator (or people making regular contributions to the SVN repository) needs to have a source forge account.
> Then when the project is registered by someone they need to add the appropriate people as developers and project administrators.
> 
> I did a bit of searching and found the old accessgrid project. This complicates creating a new one from scratch only in the fact we can't use the same name again unless the old project is removed. Alternatively we could simply give the project a different name. What are your suggestions on what we should do about this?
> 
> Committing to the source forge svn server is pretty much the same as any other one. We won't be able to carry the history of the previous svn repository unless we get a tarball of the server side of the repository. We could just ignore the history and just commit our current set of code without retaining the change history. I'd say this is probably preferable anyway as older previous revisions will be of very limited use to us anyway.
> 
> Cheers
> Andrew
> 
> 
>