all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: Adding advisory notification for non-ELPA package.el downloads
Date: Sun, 9 Jul 2017 03:39:45 +0300	[thread overview]
Message-ID: <371dc591-fc65-61b9-3eda-be09a5e653a8@yandex.ru> (raw)
In-Reply-To: <E1dTt8y-0007rQ-W0@fencepost.gnu.org>

On 7/8/17 8:03 PM, Richard Stallman wrote:

> They get into that situation because developers accept contributions
> without thinking of legal papers.  They get contributions from one
> person, then another, then another 50 people, then another 50.

It's not that serious. Most packages are created and maintained by a 
single developer, with only minor contributions from users.

There are big ones where that's not true, but they older, and they have 
surely considered going the ELPA route already.

> The way to avoid this is by showing people what the situation is like
> and how they can avoid it.  We need to educate the whole Emacs Lisp
> development community.

The nagging approach can just as likely alienate users. We already have 
a lot of those that scoff at the conditions of contributing to Emacs. 
Saying that the hassle is negligible (and saying that often, in users' 
faces) is unlikely to improve the situation.

It's better to work on streamlining the copyright assignment process and 
have a separate campaign (outside of our precious Emacs) to encourage 
developers to do it.

> That notice approach won't be effective, because people would only see
> the notice when they have a package ready to use.  That is too late.
> We want people to think of this when they START developing the
> package.

This distinction doesn't matter much. When someone starts developing a 
package, and until they publish it, they work alone in 99.9% cases.

> To inform Emacs users when they load a package from outside ELPA would
> be more effective, because they would see it earlier -- well before
> they think about putting it in a repository.
> 
> That approach would do the job, but it is not perfect.  It is not
> perfectly targeted.

I think it would be targeted perfectly: "Want to publish a package? 
Here's what you need to do to publish it where *every* Emacs user will 
be able to install it from!"

> Here's an idea that might be better targeted.
> 
> The idea is to display a notice when the user edits a file in Emacs
> Lisp mode (other than .emacs).  The code could avoid displaying the
> notice more than once per week -- using a timestamp for the last time
> it was displayed.

You might want to consider the idea that public relations is not your 
best skill.



  parent reply	other threads:[~2017-07-09  0:39 UTC|newest]

Thread overview: 96+ 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 [this message]
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
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
  -- strict thread matches above, loose matches on Subject: below --
2017-07-20 12:29 Adding advisory notification for non-ELPA package.el downloads Paul Rankin
2017-07-20 12:37 ` Clément Pit-Claudel
2017-07-20 13:42 ` Eli Zaretskii
2017-07-20 13:49   ` Jean-Christophe Helary
2017-07-20 14:17     ` Eli Zaretskii
2017-07-20 14:48       ` Jean-Christophe Helary
2017-07-20 14:57         ` Eli Zaretskii
2017-07-24  2:52       ` Richard Stallman
2017-07-20 14:01   ` Paul Rankin
2017-07-20 14:20     ` Eli Zaretskii
2017-07-20 14:36       ` Paul Rankin
2017-07-20 14:47         ` Jean-Christophe Helary
2017-07-20 15:09           ` Paul Rankin
2017-07-20 15:08         ` Eli Zaretskii
2017-07-20 15:58           ` Paul Rankin
2017-07-20 17:56             ` Eli Zaretskii
2017-07-21 11:21               ` Nikolaus Rath
2017-07-20 14:27     ` John Wiegley
2017-07-20 15:19 ` Stephen Berman
2017-07-20 16:19 ` Radon Rosborough
2017-07-24  2:52   ` Richard Stallman
2017-07-24  3:05     ` Radon Rosborough
2017-07-25  1:32       ` Richard Stallman
2017-07-20 21:20 ` 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

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

  git send-email \
    --in-reply-to=371dc591-fc65-61b9-3eda-be09a5e653a8@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.