Re: SourceForge vs Savannah

[chris <spamoff.danx@ntlworld.com>]

Stephen Leake wrote:
> chris <spamoff.danx@ntlworld.com> writes:
> 
>>I'd rather use Savannah than SF for anything.  SF keep changing their
>>T&C's and I've lost track of what's what on there.
> 
> Could you expand on this? What's "T&C". Hmm - Terms & Conditions?

Yeah, Terms and Conditions.  (I forget what it's really called!  Is it 
ToU (terms of use), tos (terms of service) or ...?),  I have a slot on 
there for a really old dead project, but about every two months I get an 
email saying SF haved changed the conditions.  About a year ago I heard 
sf.net where trying to benefit from others code by trying to take 
ownership of it in the T&C's.  I don't know if it's true, but given that 
they keep changing the T&C's and it's hard to keep up, I've been 
avoiding them.


> I'm considering moving my library to either SourceForge or Savannah. I
> was leaning towards Savannah, but then someone pointed out that being
> on SourceForge makes it easier for others to find, which is an
> important point.

True.  Savannah is less well known than sf.net.  Do a bit of research 
before picking one.  You might get bitten by sf or savannah and be 
better off on your own.  If you do pick one of these and have some kind 
of version control (CVS?) I'd be interested in how to transfer 
everything up there so people can access the entire history of the 
project (most of my code is in CVS from the beginning).


>>I would be willing to submit some of my work provided I got the
>>ability to work on it and extend it.  I would even be willing to hand
>>over my copyright, again providing I got the ability to play with it
>>(also some credit) and it was some kind of group.
> 
> That's what licensing is all about. The GPL, or the GMGPL, gives you
> what you are asking for. 

Yes, but I think Frank was suggesting a unified distribution of things. 
  What happens if people own different bits of something that is 
distributed?  There are all sorts of complications arising from 
differences in license for various bits.  A copyright owner can usually 
change the license, but the person who puts all the bits together cannot 
change the license of the separate bits to a single license.


Chris