|
| From: | Dmitry Gutov |
| Subject: | Re: Adding advisory notification for non-ELPA package.el downloads |
| Date: | Mon, 10 Jul 2017 16:02:26 +0300 |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:54.0) Gecko/20100101 Thunderbird/54.0 |
On 7/10/17 12:27 PM, Richard Stallman wrote:
I'm talking about packages that will get into this state in the future, which at present have just one developer, but will have more.
These can be well served by having the discussed call to action somewhere near (before or after) MELPA package publishing instructions.
Maybe that wasn't stated clearly at first.
It was. And I believe I've addressed it already.
> The nagging approach can just as likely alienate users. A message at most once a week, that is on the screen for a short time, is hardly "nagging".
It's an ill-defined task, at best. Which files, when, where to store the last message date? Will it distract the user from writing code (will it make the buffer contents jump)? How will it deal with personal configurations (which people have no intention of publishing), and will it continue to show those messages even after the package is published?
| [Prev in Thread] | Current Thread | [Next in Thread] |