From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Jean Louis Newsgroups: gmane.emacs.devel Subject: Re: Adding advisory notification for non-ELPA package.el downloads Date: Thu, 13 Jul 2017 18:07:57 +0300 Message-ID: <20170713150756.GA4802@protected.rcdrun.com> References: <2CCFB38C-4D19-4330-91C4-CF00EEDB58D6@gmail.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1499960244 24576 195.159.176.226 (13 Jul 2017 15:37:24 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 13 Jul 2017 15:37:24 +0000 (UTC) Cc: Jean-Christophe Helary , Emacs-Devel devel To: Tim Cross Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jul 13 17:37:20 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dVgB6-0006BV-DJ for ged-emacs-devel@m.gmane.org; Thu, 13 Jul 2017 17:37:20 +0200 Original-Received: from localhost ([::1]:60743 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dVgBB-0007nF-St for ged-emacs-devel@m.gmane.org; Thu, 13 Jul 2017 11:37:25 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41441) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dVfqQ-0006H4-9Q for emacs-devel@gnu.org; Thu, 13 Jul 2017 11:15:59 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dVfqM-000609-4V for emacs-devel@gnu.org; Thu, 13 Jul 2017 11:15:58 -0400 Original-Received: from stw1.rcdrun.com ([217.170.207.13]:50063) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dVfqL-0005jE-T8 for emacs-devel@gnu.org; Thu, 13 Jul 2017 11:15:54 -0400 Original-Received: from protected.rcdrun.com (localhost [::1]) (AUTH: PLAIN securesender, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by stw1.rcdrun.com with ESMTPSA; Thu, 13 Jul 2017 08:16:17 -0700 id 00000000000A0603.0000000059678EC2.00006E26 Original-Received: from localhost (localhost [127.0.0.1]) (uid 1001) by protected.rcdrun.com with local; Thu, 13 Jul 2017 18:07:57 +0300 id 00000000000E08F2.0000000059678CCD.000014FE Content-Disposition: inline In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 217.170.207.13 X-Mailman-Approved-At: Thu, 13 Jul 2017 11:37:16 -0400 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:216582 Archived-At: On Sun, Jul 09, 2017 at 08:50:53AM +1000, Tim Cross wrote: > Totally agree. If we want people to 'do the > right thing', we have to make it as easy as > possible. If things are as bad as Clement > indicates, nagging users will have little impact > and what impact it does have will likely be > negative. > > WRT Richard's suggestion about a weekly notice > when editing elisp files - not sure if it should > be all elisp files or whether it should be > restricted to files like *-pkg.el that are part > of package.el packages? I do a fair amount of > elisp which does not use package.el, so notices > about ELPA are just annoying. Maybe we could > modify package.el to make it mandatory for > packages to include a file/statement which > maintainers must include which requires them to > acknowledge the benefits of free software and > the disadvantages of non-ELPA repositories. What developers of GNU Emacs could do is to have yet another HELP menu item, "How to contribute", where the full instructions and updated file may be displayed in the manner of Emacs News or "How to display bugs". The menu "How to contribute" should be there all the time. I do not think that users editing *.el files shall be bothered. But they can be bothered on the Splash screen which could link to "How to contribute" file and on other screns, there could be link to "How to contribute". Same links could explain the problem with copyrights and proper assignments. And the same section could be included in Emacs Lisp and Emacs manuals. That way larger number of people would understand that they can directly contribute and they would have not just a short notice, but full explanation. Jean Louis