I have been trying to work with Sourceforge to do this. But Opera and SF were not playing nicely together. Not sure what the deal was/is, but I will try again today. I think what I want to do (and you can suggest otherwise, if you would like) is create a repository with directories for each project, and a common dir and allow the teams to keep things up under that as they wish. Also - does anyone object to using Be's makefile-engine? >I don't know how many hats Michael will want to wear, but we will need >someone to prune & shape our source code repository, as well as keeping >track of developers on SourceForge. We will want to have some organization >to the code and will want to keep makefiles for building all the code, etc. > >I think this is something I'd like to do if Michael doesn't want the job. > >- Jason > >----- Original Message ----- >From: "Marcus Overhagen" <dos4gw@xxxxxx> >To: <openbeos@xxxxxxxxxxxxx> >Sent: Friday, September 07, 2001 5:01 PM >Subject: [openbeos] Re: libscreensaver.so Proof of Concept > > >> >> On Thu, 06 Sep 2001 08:30:56 PM, Jeremy Friesner <jaf@xxxxxxxxxxxx> wrote: >> > >> >Is there a CVS server or something similar to check source code into >> >and out of? I don't think a project like this will be possible without >one.... >> >> You are correct. I think we should use the cvs available at sourceforge. >> But Michael Phipps would need to set this up for us, I think. >> I'm not familiar with cvs, but I'm quite sure that we need it. >> We also need to make sure that only the developers do check ins, >> so I think password are needed, probalby we need all to register >> at sourceforge. >> >> Michael, what do you say? >> >> regards >> Marcus