[Savannah-help-public] [sr #105871] How do I change the License of a project?

2007-06-04 Thread Sylvain Beucler

Follow-up Comment #11, sr #105871 (project administration):

Ah, you need to ask us for changing the license that is displayed in the
project page.

Note that we accept the GNU GPL starting with v2, so it would be "GPL v2 or
later".

Is that fine by you?


"If I understand you correctly, the modified BSD copyright let me distribute
BSD-code under the GPL."

Indeed.

"Another question, when I change something in a file, do I simply add a line
that says "(C) 2007 John Doe" or similar? I assume its apropiate to add a few
lines on what I changed, and that my changes are under the "GPLv1 or later"?"

If you change the license, you could:

- add a README file (or similar) in your repository that contains the
original BSD notice, stating that your code includes portion of code
originaly released under the BSD license.

- change the source file's license notice to the standard GNU GPL header

- keep the existing copyright notices in the source file and add your own
after them

I did something similar in GNU FreeDink:
http://cvs.savannah.gnu.org/viewvc/freedink/doc/legal-notices_orig.txt?revision=1.1&root=freedink&view=markup
http://cvs.savannah.gnu.org/viewvc/freedink/freedink.cpp?revision=1.2&root=freedink&view=markup


___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/





[Savannah-help-public] fencepost.gnu.org maintenance / relocation

2007-06-04 Thread Justin Baugh
Over the next few days, fencepost will be shut down for maintenance a 
few times to receive some upgrades as well as so it can be moved to a 
new network.


On Wednesday, June 6, 2007, at 11:00 AM GMT -0400, fencepost will be 
down for an hour while we reallocate disk space and install new memory.


On Thursday, June 7, 2007, at 11:00 AM GMT -0400, fencepost will be down 
for approximately two hours while the machine is relocated to a 
different facility and moved to a new network. DNS changes reflecting 
this should be quick to propagate, but for reference, the new IP address 
of fencepost.gnu.org will be 140.186.70.10. Users should notice 
significant speed increases as fencepost will be moving from its 
traditional home behind FSF's T1 line to a new multihomed BGP-routed 
network with over 400Mbps of bandwidth available to it.


Questions about this upgrade/migration should be directed to 
[EMAIL PROTECTED]


Thanks,

-Justin

--
Justin Baugh (baughj at gnu dot org)
Senior Systems Administrator
Free Software Foundation





Re: [Savannah-help-public] Radius SVN repository

2007-06-04 Thread Sylvain Beucler
Hi,

On Tue, May 29, 2007 at 04:14:58PM +0300, Sergey Poznyakoff wrote:
> [My apologies for not being able to respond earlier.]
> 
> Sylvain Beucler <[EMAIL PROTECTED]> ha escrit:
> 
> > > gateway.  Only one more question: what data store type is being used?
> > 
> > We use FSFS, which is svn's default now. Apparently there's bad
> > feedback with DBD which may need to be repaired from time to time.
> 
> In that case, could you please convert Radius repo to SVN?
>  
> > I wasn't about to work on it right now but maybe I can change. What
> > are your plans and how far did you go?
> 
> Well, I have almost finished commit email notifications (the stuff is
> on testing stage now).  I guess I'll be able to show the results by
> this weekend.  As for the plans, I am thinking about cvs-to-svn
> gateway, it looks like a useful feature.  What do you think?

Sorry for the lag, I've been busy finishing a Savane clean-up
(register_globals, magic_quotes, mysql sanitizing, PHP warnings...)
branch I started some months ago.
(http://svn.savannah.nongnu.org/viewvc/trunk/?root=administration)

What did you cover wrt email notifications? Is this a backend
improvement, or is there also a frontend to manage them? I started
doing something to manage CVS hooks.

About the gateway: at Savannah, Jim Meyering is working on installing
one for Git (git-cvspserver). I don't know exactly what this means for
SVN.  We plan to install it on a different IP, because we don't plan
to drop CVS in favor of git site-wide ;) I don't think this really
concerns Savane though. Maybe you mean a CVS->SVN auto converter,
which would be nice, given a generic job queue management.

-- 
Sylvain