public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: dberlin@dberlin.org
Cc: gcc@gcc.gnu.org
Subject: Re: please update the gcj main page
Date: Mon, 01 Aug 2005 03:17:00 -0000	[thread overview]
Message-ID: <10508010320.AA14390@vlsi1.ultra.nyu.edu> (raw)

    You don't really need copyright assignment (IE you can go along with
    just licenses) unless you plan on suing people over your documentation,
    which seems even less likely than suing someone over your code.

I don't follow.  The issue is that somebody claims that the FSF documentation
infringes on their copyright and claims that the disclaimers on the Wiki do
not constitute a contract or license.  It would be very embarassing to the
FSF to be found guilty of copyright infringement and it doesn't matter
whether it's in code or documentation.

    Forcing people to write more documentation will only work if it's not
    really extra work for them.

Again, I don't follow.  Writing documentation certainly is "extra work".
Indeed it's often much more work than writing the code.  But it's a very
critical part of software development and if people aren't willing to do it,
their contribution isn't very valuable.

             reply	other threads:[~2005-08-01  3:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-01  3:17 Richard Kenner [this message]
2005-08-01  3:41 ` Daniel Berlin
  -- strict thread matches above, loose matches on Subject: below --
2005-07-14 17:02 John M. Gabriele
2005-07-15  7:18 ` Ranjit Mathew
2005-07-15 15:21   ` John M. Gabriele
2005-07-15 15:43     ` Bryce McKinlay
2005-07-15 16:47       ` John M. Gabriele
2005-07-15 15:29   ` Bryce McKinlay
2005-07-15 16:39     ` John M. Gabriele
2005-07-15 16:57       ` Andrew Pinski
2005-07-15 20:48     ` Tom Tromey
2005-07-31 22:30       ` Gerald Pfeifer
2005-07-31 23:00         ` Daniel Berlin
2005-07-31 23:02           ` Gerald Pfeifer
2005-07-31 23:17             ` Daniel Berlin
2005-07-31 23:31               ` Gerald Pfeifer
2005-08-01  2:50                 ` Robert Dewar
2005-08-01  3:08                   ` Daniel Berlin
2005-08-23  8:48                 ` Florian Weimer
2005-08-23 16:53                   ` John M. Gabriele
2005-07-31 23:12         ` Joseph S. Myers
2005-07-31 23:19           ` Daniel Berlin

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

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

  git send-email \
    --in-reply-to=10508010320.AA14390@vlsi1.ultra.nyu.edu \
    --to=kenner@vlsi1.ultra.nyu.edu \
    --cc=dberlin@dberlin.org \
    --cc=gcc@gcc.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).