Mon Sep 27 20:54:32 2010, comment #6:
Paul responded on the list, again here are my responses:
I'll try get to this - I'll probably be a little busy this week and next. If you want to proceed with it, that'd be great. I'm confident I and others will fix the issues soon. Setting up the Savannah project will allow me to get other maintainers involved on this.
Fine, I will approve it right away. I will keep the task open so you can notify us when you are ready for a review in the version control system of your choice.
The one issue we were thinking to not fix though is putting the full-sized GPL headers into /all/ the files. There are certain files where this is overkill and not warranted (e.g. because unlicensed copying of just that file will never ever be something that would bother us), e.g. the NEWS and TODO files. We're thinking instead to add a short, one-liner to remind the reader the file is available for distribution under the terms in the accompanying COPYING file.
Again, please think not about you prosecuting infringements, but about downstream redistributors worrying about file provenance. If e.g. Debian picks up the package they will be more comfortable if they can audit the license for every file, silly as it may be, and be assured that they can legally distribute all files. The one-liner is probably fine for this purpose.
Thanks, and enjoy your stay on Savannah!
I've approved your project--welcome on board! :-)
You'll receive a mail notification with further instructions shortly.
--
Happy hacking!
|
Sun Sep 19 21:46:27 2010, comment #4:
Hi,
Paul responded on the savannah-register-public mailing list, so I am including his replies here and answering too.
Oops, yes.
- Some documentation files (NEWS, README, Changelog...) lack the required GPL header.
The ChangeLog file is deprecated iirc. We'll remove it. For stuff like a README file, I'm not eniterly sure it makes sense to add a GPL header - it would detract from the immediacy of the content. Further, I do not anticipate ever caring about copyright infringement on such files, and anyway it should already be clear from the COPYING file that these are GPLed (the header is added to more important files, like C source, just to ensure readers can't miss the fact).
For the README file, you can always add the license header at the bottom so as to keep it readable. Keep in mind that we have to worry not only about copyright infringement, but also about protecting all users of the package. Having clear copyright assignments helps make the status of each file legally sound.
- There are a few PNG files in there, but it's not clear where they come from. The best solution is usually to state in the README or some similar file the license for each one.
You're probably looking at a 'make dist' tarball, and the PNGs come from the 'Dia' files in the same directory, I think.
Probably, so these aren't needed? In this case they can just be removed safely, right?
- Please upload a new tarball with these issues solved, and let us know when it's ready for a new review, OK?
Ok, that will take a week or so - am on holidays. ;)
Good for you, the task will be left open.
- Finally, you say that Quagga is a fork of GNU Zebra; while forks are sometimes necessary (and GNU Zebra seems to have stopped development in 2005), it might be better to help the original package move along. Have you contacted the authors of GNU Zebra, and/or the GNU project, to see if they would like some contributors?
Yes we did. We were in contact with RMS and the FSF about this even before the fork - which was quite a while ago. The original GNU project is mostly dead in terms of community and development, relative to Quagga. Unfortunately, they were not willing to hand the project on.
As per Karl, things just are as they are in this regard.
That is fine then.
I'll try address your issues soon. I will probably submit a tarfile without the auto-generated bits next time (maintainer clean kind of thing).
If you think this can take too long you are free to close this task and resubmit when you are ready; whatever suits you better.
|
Mon Sep 6 17:14:04 2010, comment #2:
Alex, you're right in general to mention the possibility of collaborating with an existing package (like GNU Zebra). However, in this particular case Paul and I have exchanged many emails over many years about the situation, and it seems the two packages have to remain separate for the foreseeable future, unfortunately.
|
Sun Sep 5 21:22:52 2010, comment #1:
Hi Paul,
Sorry for the delay; there is a bit of a backlog after the summer Holidays. I am reviewing your submission on behalf of Savannah, and there are a few issues with it:
- You speak about "Linux", but we prefer that you use "GNU/Linux": it gives credit to the GNU project besides the Linux kernel. Read the Hosting requirements for more details.
- Some documentation files (NEWS, README, Changelog...) lack the required GPL header.
- There are a few PNG files in there, but it's not clear where they come from. The best solution is usually to state in the README or some similar file the license for each one.
Please upload a new tarball with these issues solved, and let us know when it's ready for a new review, OK?
Finally, you say that Quagga is a fork of GNU Zebra; while forks are sometimes necessary (and GNU Zebra seems to have stopped development in 2005), it might be better to help the original package move along. Have you contacted the authors of GNU Zebra, and/or the GNU project, to see if they would like some contributors?
Thanks, Alex.
|
Sat Jul 10 08:06:09 2010, original submission:
A new project has been registered at Savannah
This project account will remain inactive until a site admin approves or discards the registration.
Registration Administration
While this item will be useful to track the registration process, approving or discarding the registration must be done using the specific Group Administration page, accessible only to site administrators, effectively logged as site administrators (superuser):
Registration Details
- Name: Quagga Routing Software
- System Name: quagga
- Type: non-GNU software & documentation
- License: GNU General Public License v2 or later
Description:
Quagga is a routing software suite, providing implementations of OSPFv2, OSPFv3, RIP v1 and v2, RIPng and BGP-4 for Unix platforms, particularly FreeBSD, Linux, Solaris and NetBSD. Quagga is a fork of GNU Zebra which was developed by Kunihiro Ishiguro.
Other Software Required:
GNU Readline, GPLv3, http://cnshttp://www.cns.cwru.edu/php/chet/readline/rltop.html
ncurses, MIT, http://invisible-island.net/ncurses/ncurses.html
Net-SNMP (optional), BSD / MIT, http://net-snmp.sourceforge.net/
Tarball URL:
http://www.quagga.net/download/quagga-0.99.16.tar.gz
|