savannah-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Savannah-hackers] submission of The Quantum Coreworld - savannah.no


From: Sylvain Beucler
Subject: Re: [Savannah-hackers] submission of The Quantum Coreworld - savannah.nongnu.org
Date: Wed, 29 Sep 2004 16:27:22 +0200
User-agent: Mutt/1.4.2.1i

Is there a new version with fixes now?

-- 
Sylvain

On Mon, Sep 06, 2004 at 11:45:08AM -0400, Alexander (Sasha) Wait wrote:
> On Sun, 2004-09-05 at 18:02, Sylvain Beucler wrote:
> > Can you add explicit copyright and license notices to these documents?
> > If verbosity is an issue, check
> > http://www.gnu.org/licenses/fdl-howto.html for a smaller notice that
> > refers to the main document (if you have one).
> > 
> OK 
> 
> > Moreover, you cannot include coreworld-standard.txt at Savannah until
> > you are sure that you can distribute it under the GNU GPL.
> > 
> I will contact the copyright holders (if I can).  The original
> "standard" was posted to Usenet without a copyright notice.  One might
> think it is in the public domain but I am not a lawyer.    
> 
> > I see a small non-standard GDFL notice:
> > "with the Invariant Sections being just Philosophy and Acknowledgements"
> > 
> > The word 'just' should not be included; the GFDL permits to add
> > Invariant section in future releases, and it could be misinterpreted.
> > 
> > Also, you do not need to explicitely cite Acknowledgements, as it is
> > already covered by section 4.K of the GNU FDL.
> > 
> > Each part of the document should carry a small copyright+license
> > notice as described in http://www.gnu.org/licenses/fdl-howto.html
> > 
> OK
> 
> > Last, you need to include a full copy of the GNU FDL along with your
> > document.  The GPL FAQ explains why these procedures must be followed.
> > For example, to learn why a copy of the GPL must be included with
> > every copy of the code, for example, go to
> > http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude
> > 
> > Don't feel sorry for adding that document, it is my job to point to
> > good licensing practices ;)
> > 
> Thanks for all the information! 
> 
> > Elfyn is working on Arch, and we already began discussing the problem
> > Arch brings (namely, the fact that the repository is accessible by
> > SFTP, with less repository protection than with CVS).
> > 
> > I won't hide you that we have other issues with higher priority at the
> > moment, but be sure we are interested in supporting Arch :)
> 
> It's good to hear you may support Arch in the future.  I'm writing a
> document about "Managing the Quantum Coreworld Project with GNU Arch". I
> hope it will be generic enough to be useful to others. Early draft at: 
> 
>       * 
> http://wiki.gnuarch.org/moin.cgi/Managing_20the_20Quantum_20Coreworld_20Project_20with_20GNU_20Arch




reply via email to

[Prev in Thread] Current Thread [Next in Thread]