unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John Darrington <john@darrington.wattle.id.au>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org, John Darrington <jmd@gnu.org>
Subject: Re: [PATCH 3/4] gnu: Add German Aspell dictionary.
Date: Sun, 28 Aug 2016 14:41:04 +0200	[thread overview]
Message-ID: <20160828124104.GA27453@jocasta.intra> (raw)
In-Reply-To: <20160828092045.GG26988@macbook42.flashner.co.il>

[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]

On Sun, Aug 28, 2016 at 12:20:45PM +0300, Efraim Flashner wrote:
     > +(define-public aspell-dict-de
     > +  (aspell-dictionary "de" "German"
     > +                     #:version "20030222-1"
     > +                     #:sha256
     > +                     (base32
     > +                      "01p92qj66cqb346gk7hjfynaap5sbcn85xz07kjfdq623ghr8v5s")))
     don't forget your copyright line. Otherwise looks good.
     
I didn't forget.  But I don't consider these 6 lines to be in any respect
novel, creative or original.  The FSF guidelines for what is regarded as
"legally significant" for copyright purposes mentions the limit of 15 lines.

In fact, I challenge anyone to offer a definition of aspell-dict-de which
works in Guix AND satisfies our rather strict coding style, and does not
differ from the above, except in whitespace.

In other words, there is nothing novel or creative in what I have written.
Thus, is would be dishonest (perhaps illegal?) for me to claim copyright on
this work.

J'

-- 
Avoid eavesdropping.  Send strong encryted email.
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2016-08-28 12:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-27 18:19 [PATCH 1/4] gnu: yelp: Update to 3.21.3 John Darrington
2016-08-27 18:19 ` [PATCH 2/4] CoC: Correct punctuation John Darrington
2016-08-28  9:19   ` Efraim Flashner
2016-08-28  9:52     ` John Darrington
2016-08-30  1:52       ` Leo Famulari
2016-08-27 18:19 ` [PATCH 3/4] gnu: Add German Aspell dictionary John Darrington
2016-08-28  9:20   ` Efraim Flashner
2016-08-28 12:41     ` John Darrington [this message]
2016-08-29  8:35       ` Alex Kost
2016-08-29 16:50         ` Ludovic Courtès
2016-08-27 18:19 ` [PATCH 4/4] gnu: libtirpc: Remove the --disable-gssapi configure flag John Darrington
2016-08-28  9:43   ` Efraim Flashner
2016-08-28  9:45     ` John Darrington
2016-08-29 16:52       ` Ludovic Courtès
2016-08-29 19:51         ` John Darrington
2016-09-02 13:16 ` [PATCH 1/4] gnu: yelp: Update to 3.21.3 Ludovic Courtès
2016-09-02 14:56   ` John Darrington
2016-09-03 13:57     ` Ludovic Courtès
2016-09-03 14:28       ` John Darrington

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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=20160828124104.GA27453@jocasta.intra \
    --to=john@darrington.wattle.id.au \
    --cc=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=jmd@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).