unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mathieu Roy <yeupou@gnu.org>
Cc: savannah-hackers@gnu.org
Subject: Re: Are Matrix extension for Guile and FFTW part of Guile?
Date: 02 Jan 2003 21:05:27 +0100	[thread overview]
Message-ID: <m3y963xqpk.fsf@gnu.org> (raw)
In-Reply-To: <xy7fzsbjsf0.fsf@nada.kth.se>

Mikael Djurfeldt <djurfeldt@nada.kth.se> said:

> Mathieu Roy <yeupou@gnu.org> writes:
> 
> > Mikael Djurfeldt recently asked reclassification of the projects "FFTW
> > bindings for Guile" and "Matrix extension for Guile" to the GNU
> > category on Savannah, as they were in the non-GNU category.
> >
> > http://savannah.gnu.org/projects/guile-fftw/
> > http://savannah.gnu.org/projects/guile-matrix/
> >
> > The main reason was the fact that thoses extensions are Guile
> > extension. I understood that it was official Guile extension, official
> > part of the Guile project, and so, official part of the GNU project. 
> >
> > Today, someone noticed that we are absolutely not sure that thoses
> > extensions are subprojects of the Guile project.
> >
> > So the question is : are thoses extensions part of the Guile project,
> > and so should remains as GNU, or is it a misunderstanding and should
> > they be, one more time, reclassified?
> 
> guile-fftw and guile-matrix are projects initiated by me and are not
> officially parts of Guile.  I have never claimed that they are before
> this message.

Ok. 
But in fact, I wrongly assumed that you were saying that they are
since if they're not, there's absolutely no reason to consider them
GNU package.
 
> But, guile-fftw and guile-matrix are extensions to Guile and since
> I've assigned copyright to the FSF for all extensions to Guile which
> I write, I don't see why there should be any problem in denoting
> them as GNU projects.  What more than that is required?

Assigning copyright and making a project part of the GNU project are two
differents things. 

Assigning copyright can be usefull to fix potential legal issues and
to let FSF taking care of license violation while making a project
part of the GNU project means following GNU standards and being
approved by the GNU project (in fact, by Richard Stallman).  
  
> If it is necessary for legal reasons I hereby, as an official Guile
> developer, declare guile-fftw and guile-matrix to be official parts
> of the Guile project.

So if others people of Guile project accept this, this issue is over.

You should read carefully the following page 
http://www.gnu.org/evaluation/evaluation.html

Regards,

-- 
Mathieu Roy
 
 << Profile  << http://savannah.gnu.org/users/yeupou <<
 >> Homepage >> http://yeupou.coleumes.org           >>
 << GPG Key  << http://stock.coleumes.org/gpg        <<


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2003-01-02 20:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-02 17:34 Are Matrix extension for Guile and FFTW part of Guile? Mathieu Roy
2003-01-02 18:52 ` Mikael Djurfeldt
2003-01-02 20:05   ` Mathieu Roy [this message]
2003-01-02 22:34     ` Marius Vollmer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3y963xqpk.fsf@gnu.org \
    --to=yeupou@gnu.org \
    --cc=savannah-hackers@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).