unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk (Phillip Lord)
To: "Etienne Prud’homme" <e.e.f.prudhomme@gmail.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: Improving GNU ELPA
Date: Thu, 13 Jul 2017 23:07:01 +0100	[thread overview]
Message-ID: <87k23cng8q.fsf@russet.org.uk> (raw)
In-Reply-To: <87eftkb0xr.fsf@x230.lts> ("Etienne Prud’homme"'s message of "Thu, 13 Jul 2017 15:18:24 -0400")

Etienne Prud’homme <e.e.f.prudhomme@gmail.com> writes:

> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> PS: BTW, to clarify my position: if it were up to me, I'd get rid of the
>>     copyright assignment policy for GNU ELPA (and for Emacs as well,
>>     while we're at it), but I'd keep the "locally hosted in a repository
>>     to which we have write access, with commit-diffs".
>
> Making a web application for describing the need and the process of the
> paperwork.  I mean by that a simple 3-4 clicks process.

A web interface with an current status and easy navigation would be a
great addition, I think.


> 3. validate the information to send and that the employer would allow
>    such thing.  In case the work might be done on the company’s time,
>    ask a confirmation from the company (similar to step 2).

It's irrelevant when the work is done unfortunately. If you are employed
as a programmer, then a priori your employer has a strong claim on the
copyright of any code you right.

So, you have to get a disclaimer. This is one of those things that can
take quite a while, especially if you work for a big company.


> All of those things could be done from the web browser (and also from
> Emacs).  We could make a web application for that that could be used by
> other projects.  A copyright assignment could be done in 5min.

It's worth a try for sure!

Phil




  reply	other threads:[~2017-07-13 22:07 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-08  1:59 Adding advisory notification for non-ELPA package.el downloads John Wiegley
2017-07-08 10:29 ` Dmitry Gutov
2017-07-08 12:57   ` Kaushal Modi
2017-07-08 17:03   ` Richard Stallman
2017-07-08 22:12     ` Jean-Christophe Helary
2017-07-08 22:50       ` Tim Cross
2017-07-10  9:29         ` Richard Stallman
2017-07-13 15:07         ` Jean Louis
2017-07-10  9:29       ` Richard Stallman
2017-07-09  0:39     ` Dmitry Gutov
2017-07-10  2:07       ` Chad Brown
2017-07-10  9:27       ` Richard Stallman
2017-07-10 13:02         ` Dmitry Gutov
2017-07-11 11:45           ` Richard Stallman
2017-07-11 15:00             ` Yuri Khan
2017-07-11 18:01               ` John Wiegley
2017-07-11 18:37                 ` Yuri Khan
2017-07-11 22:57               ` Richard Stallman
2017-07-12  7:56                 ` Yuri Khan
2017-07-12 16:12                   ` Richard Stallman
2017-07-12 17:49                     ` emacs.org website [was Re: Adding advisory notification for non-ELPA package.el downloads] Glenn Morris
2017-07-13 12:23                       ` Richard Stallman
2017-07-15  5:55                         ` John Wiegley
2017-07-12 16:35                   ` Glenn Morris
2017-07-11 22:57               ` Adding advisory notification for non-ELPA package.el downloads Richard Stallman
2017-07-12 23:12                 ` Nicolas Petton
2017-07-13 12:26                   ` Richard Stallman
2017-07-13 19:12                     ` Nicolas Petton
2017-07-15  1:33                       ` Richard Stallman
2017-07-17  8:16                         ` Nicolas Petton
2017-07-24  2:54                           ` Richard Stallman
2017-07-10 15:36         ` Ken Manheimer
2017-07-10 23:32           ` Richard Stallman
2017-07-08 14:57 ` Clément Pit-Claudel
2017-07-09  3:04   ` Yann Hodique
2017-07-10  9:29     ` Richard Stallman
2017-07-10 15:41       ` Ken Manheimer
2017-07-10 23:30         ` Richard Stallman
2017-07-10 16:48       ` Yann Hodique
2017-07-10 20:43   ` Joost Kremers
2017-07-11 22:57     ` Richard Stallman
2017-07-12  0:40       ` Stefan Monnier
2017-07-12 16:13         ` Richard Stallman
2017-07-11 16:04   ` Improving GNU ELPA (was: Adding advisory notification for non-ELPA package.el downloads) Stefan Monnier
2017-07-12  1:26     ` Improving GNU ELPA Clément Pit-Claudel
2017-07-12  2:19       ` Stefan Monnier
2017-07-12 23:17         ` Nicolas Petton
2017-07-13  2:03           ` Stefan Monnier
2017-07-13  2:07             ` Stefan Monnier
2017-07-13 19:18         ` Etienne Prud’homme
2017-07-13 22:07           ` Phillip Lord [this message]
2017-07-16 16:04     ` Improving GNU ELPA (was: Adding advisory notification for non-ELPA package.el downloads) Jonas Bernoulli
2017-07-16 17:11       ` Improving GNU ELPA Stefan Monnier
2017-07-16 17:28         ` Jonas Bernoulli
2017-07-17 16:46           ` Phillip Lord
2017-07-17 18:26           ` Stefan Monnier
2017-07-17 21:04             ` Richard Stallman
2017-07-17 21:21               ` Stefan Monnier
2017-07-18 10:08                 ` Phillip Lord
2017-07-18 13:35                   ` Stefan Monnier
2017-07-18 16:17                     ` Phillip Lord
2017-07-18 14:18                   ` Richard Stallman
2017-07-18 16:23                     ` Phillip Lord
2017-07-19  3:31                       ` Richard Stallman
2017-07-19 22:54                         ` Phillip Lord
2017-07-18 14:16                 ` Richard Stallman
2017-07-18 14:39                   ` Stefan Monnier
2017-07-18 16:20                     ` Phillip Lord
2017-07-18 17:26                       ` Stefan Monnier
2017-07-19 22:59                         ` Phillip Lord
2017-07-24  2:54                           ` Richard Stallman
2017-07-24 12:26                             ` Phillip Lord

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=87k23cng8q.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=e.e.f.prudhomme@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).