unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Bastien <bzg@gnu.org>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: Copyright verification service
Date: Wed, 27 May 2020 11:21:38 +1000	[thread overview]
Message-ID: <CAC=50j8UjOc7=LiSZ0DUDHpHH4s4snxqEQcEhqYuZhCb7qou+w@mail.gmail.com> (raw)
In-Reply-To: <83mu5uvk23.fsf@gnu.org>

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

On Wed, 27 May 2020 at 00:37, Eli Zaretskii <eliz@gnu.org> wrote:

> > From: Tim Cross <theophilusx@gmail.com>
> > Date: Tue, 26 May 2020 10:02:26 +1000
> > Cc: Emacs developers <emacs-devel@gnu.org>
> >
> > My idea is that the list does stay private. You cannot see/retrieve the
> list. All you can do is submit an email
> > address and it will come back with either yes or no (ture/false etc)..
> You wold need to know the email
> > address before you can check copyright status.
>
> Richard is working with the FSF stuff on this, but AFAIU the response
> cannot be a binary YES/NO result, it must be able to return a 3rd
> value, meaning "human investigation is required".  I don't know if you
> ever saw the copyright list, but some entries there are not very
> trivial for a program to process, since they include various
> conditions that are written in free-text format which would not be
> simple for a program to parse and apply.
>

That wouldn't be an issue - you can easily define the semantics to whatever
is needed. It may also be necessary to transform/normalize the source data
and you could even set things up so that if a manual check needs to be made
for a particular email address, once that check has been performed, add
that email address with the appropriate value so that it doesn't need to be
done again. The first object here is to make the processes easier and a
good example of the 80/20 rule.
-- 
regards,

Tim

--
Tim Cross

[-- Attachment #2: Type: text/html, Size: 2139 bytes --]

  reply	other threads:[~2020-05-27  1:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25  5:46 Copyright verification service Tim Cross
2020-05-25  7:58 ` Bastien
2020-05-26  0:02   ` Tim Cross
2020-05-26 14:37     ` Eli Zaretskii
2020-05-27  1:21       ` Tim Cross [this message]
2020-05-26  0:29   ` Clément Pit-Claudel
2020-05-26  0:47     ` Tim Cross
2020-05-27  3:07     ` Richard Stallman
2020-06-01  6:59     ` Bastien
2020-06-01  7:23       ` Clément Pit-Claudel
2020-06-01  7:42         ` Bastien
2020-05-26  4:11 ` Richard Stallman

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/emacs/

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

  git send-email \
    --in-reply-to='CAC=50j8UjOc7=LiSZ0DUDHpHH4s4snxqEQcEhqYuZhCb7qou+w@mail.gmail.com' \
    --to=theophilusx@gmail.com \
    --cc=bzg@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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/emacs.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).