Registered at SourceForge... Now What?
Posted: Mon Nov 28, 2005 5:12 pm
I just got my project approved at SourceForge (wow, that was easy) so now I need to know what exactly to do. The funny thing is, mostly everything I could do with SourceForge I can do now.
Here's my predicament:
1. Alpha quality software (about 105KB when tar'red) with complete Subversion change control history on a locally hosted SVN server that also hosts some other pet projects not ready for release
2. I have webhosting and a copy of the script running on my own server, as well as a tarballed copy of it ready for distribution
So... what do I do?
Regarding:
1. Yes, SourceForge only accepts CVS, so does this mean I nix the idea of using CVS altogether and simply use SourceForge as a filemirror, but...
2. Reading SourceForge's Service Listing most of them are inapplicable
* File Release System - well, extra mirrors can't hurt, but not necessary
* Donation System - ::laughs::
* Compile Farm - PHP man!
* CVS Service - The thorny issue.. is it worth it?
* Communication Tools - maybe the mailing list would be nice, but SourceForge's forums are pretty bad. And, of course I could always put a forum on my website.
* Publicity - Nice, but I know my demographic and SourceForge probably isn't the best place to reach out to them
* Project Web Service - once again, I have web hosting, so it's nice, but not necessary
If I do decide to use their CVS, what do I do? Do I "double" version my repository, having CVS and SVN versioning them simultaneously? How do I convert the history of a single folder in my repository (not the entire one) from SVN? Should I even bother (something researching probably can't help)?
Help please!
PS - If anyone is interested (like, they're a Wikipedian), the project is called CoLocus (Community Contingency Locus). Here's an live site for the program. Source code here: Source code
Here's my predicament:
1. Alpha quality software (about 105KB when tar'red) with complete Subversion change control history on a locally hosted SVN server that also hosts some other pet projects not ready for release
2. I have webhosting and a copy of the script running on my own server, as well as a tarballed copy of it ready for distribution
So... what do I do?
Regarding:
1. Yes, SourceForge only accepts CVS, so does this mean I nix the idea of using CVS altogether and simply use SourceForge as a filemirror, but...
2. Reading SourceForge's Service Listing most of them are inapplicable
* File Release System - well, extra mirrors can't hurt, but not necessary
* Donation System - ::laughs::
* Compile Farm - PHP man!
* CVS Service - The thorny issue.. is it worth it?
* Communication Tools - maybe the mailing list would be nice, but SourceForge's forums are pretty bad. And, of course I could always put a forum on my website.
* Publicity - Nice, but I know my demographic and SourceForge probably isn't the best place to reach out to them
* Project Web Service - once again, I have web hosting, so it's nice, but not necessary
If I do decide to use their CVS, what do I do? Do I "double" version my repository, having CVS and SVN versioning them simultaneously? How do I convert the history of a single folder in my repository (not the entire one) from SVN? Should I even bother (something researching probably can't help)?
Help please!
PS - If anyone is interested (like, they're a Wikipedian), the project is called CoLocus (Community Contingency Locus). Here's an live site for the program. Source code here: Source code