Follow-up Comment #3, task #8745 (project administration): Thanks for the updated tarball. To your questions:
1) Including the text of the license is required by the GPL itself, so it's not something that we have invented. See http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude. Not all free software licenses have such a requirement (although it is often implied). 3) This looks like a wrong recommendation to me. The format of the license notice is part of the license text and should be consistent. Furthermore, the license in COPYING is GPLv3. If you want to use GPLv2+, then please include the text of version 2 -- otherwise it is a serious source of confusion. > I noticed that there's a proprietary piece of software > named scalc? What do I need to do? Probably nothing; this is not a problem as far as Savannah is concerned. If the company/entity that develops the proprietary program has registered trademark, they may ask you to change the name. This happened in the past for a few projects (e.g. Bonfire -> Brasero, Gaim -> Pidgin). _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/task/?8745> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
