unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Pierre Bernatchez <pbz@ogopogo.biz>
Subject: Re: doc license section
Date: Thu, 22 Jan 2004 13:08:25 -0500	[thread overview]
Message-ID: <40101199.8050801@ogopogo.biz> (raw)
In-Reply-To: <87n08gc2g0.fsf@zagadka.ping.de>

Marius Vollmer wrote:
> Marius Vollmer <mvo@zagadka.de> writes:
> 
> 
>>>Be aware that the feeling on the debian-legal mailing list is that the
>>>GFDL is not sufficiently free for materials in Debian [...]
>>
>>Yes, but I'm going with the FSF here, simply because Guile is a GNU
>>package.
> 
> 
> To elaborate a bit: I don't see how Guile is different from any other
> GNU package when it comes to the license of its manual.  When there
> are convincing reasons why Guile shouldn't use the FDL, no GNU package
> should use it.  This issue should be decided by the 'upper
> management', for all of GNU...
> 
This may be off topic, but since I did not bring
up the subject, I am justified in voicing a
dissenting opinion before going back
to my role of guile beginner lurking the list.

'upper management' deciding for the underlings
is the evil empire way of doing things.  If GNU
had fallen into 'upper management' oriented
methods, it would be a sign that GNU lost
sight of the objective and were morphing into
what they most oppose.

GNU's role is to provide advice, guidelines and
a rallying point, not dictating decisions.
Leadership not autocracy, the decisions are for
participants to arrive at by consensus.

GFDL raises questions for which adequate answers
have yet to be given.

Any knowing programmer infers from the word 'source' the
meaning 'source and accompanying explanations and instructions'.
So libre source includes libre documentation.

Documentation which is published under more restrictive license
further restricts the combination 'source and instructions'

What's most unclear in the GFDL, is the reason behind these
further restrictions.  The Debian group (of which I am not
a member to date) have registered some objections to the
GFDL which at least appear valid and well founded.

Your comment implies to me that rather than getting bogged
down in legal jargon religious wars, you would prefer to pick
a default choice, get on with the real work and let the
debate find its way to a conclusion somewhere else.

At first glance a sound proposition.
But you are picking the wrong default.

The correct default, pending further debate should be
the status quo, what our community has been doing all along,
publishing both source and its documentation under the same
license.

Adopting this current change in licensing as the new
default choice without further debate  is tantamount to
blind obedience.

The success of the libre software movement hinges on people
thinking for themselves.





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


  reply	other threads:[~2004-01-22 18:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-15  0:30 doc license section Kevin Ryde
2004-01-15  2:12 ` Stephen Compall
2004-01-20  0:46   ` Kevin Ryde
2004-01-15 21:37 ` Neil Jerram
2004-01-21 21:56 ` Marius Vollmer
2004-01-21 22:04   ` Carl Witty
2004-01-21 22:58     ` Kevin Ryde
2004-01-21 23:07     ` Marius Vollmer
2004-01-21 23:22       ` Marius Vollmer
2004-01-22 18:08         ` Pierre Bernatchez [this message]
2004-01-22 18:22           ` Paul Jarc
2004-01-22 23:18           ` Marius Vollmer
2004-01-21 22:13   ` Kevin Ryde
2004-01-21 22:40     ` Neil Jerram
2004-02-18 20: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=40101199.8050801@ogopogo.biz \
    --to=pbz@ogopogo.biz \
    /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).