1 |
James ha scritto: |
2 |
> Chuanwen Wu <wcw8410 <at> gmail.com> writes: |
3 |
> |
4 |
> |
5 |
>> I have written a project, which is a distribution net file system, and |
6 |
>> I want to publish it under GPL. |
7 |
>> I have source code now of course, but I don't know how to make package |
8 |
>> and publish it as a project . |
9 |
> |
10 |
> Well you can just make the code available via cvs or svn. Or you |
11 |
> can publish your code via freshmeat or sourceforge, or directly |
12 |
> off of your ftp/web server. |
13 |
|
14 |
I would strongly recommend using a public version management system if |
15 |
you want to maintain an open source project (and even a non-open one). |
16 |
|
17 |
I personally use Subversion (SVN) on Google Code; which, for my needs, |
18 |
fits well, is very well documented it is very simple to use. Google Code |
19 |
also has a very easy web interface, even if not as flexible as |
20 |
Sourceforge (but I found working with SF a bit of a pain). |
21 |
|
22 |
A lot of people praise a lot Git, so maybe you should check that out too |
23 |
before deciding (I don't know what source code repositories support Git, |
24 |
by the way). |
25 |
|
26 |
Just stay away from CVS: it is old, clunky and it is currently being |
27 |
phased out by most people. |
28 |
|
29 |
m. |