From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Yuri Khan Newsgroups: gmane.emacs.devel Subject: Re: Adding advisory notification for non-ELPA package.el downloads Date: Tue, 11 Jul 2017 22:00:53 +0700 Message-ID: References: <371dc591-fc65-61b9-3eda-be09a5e653a8@yandex.ru> <5d6bfce5-62dd-dba9-c741-e7c9ec9d166a@yandex.ru> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1499785531 32556 195.159.176.226 (11 Jul 2017 15:05:31 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 11 Jul 2017 15:05:31 +0000 (UTC) Cc: Emacs developers , Dmitry Gutov To: "rms@gnu.org" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jul 11 17:05:25 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 1dUwis-0007RJ-LB for ged-emacs-devel@m.gmane.org; Tue, 11 Jul 2017 17:05:10 +0200 Original-Received: from localhost ([::1]:46897 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dUwit-0008Ok-AT for ged-emacs-devel@m.gmane.org; Tue, 11 Jul 2017 11:05:11 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50234) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dUwgD-0007Ks-QT for emacs-devel@gnu.org; Tue, 11 Jul 2017 11:02:30 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dUwg9-0000Ar-Gg for emacs-devel@gnu.org; Tue, 11 Jul 2017 11:02:25 -0400 Original-Received: from mail-it0-f48.google.com ([209.85.214.48]:37050) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dUwg5-00008m-4K; Tue, 11 Jul 2017 11:02:17 -0400 Original-Received: by mail-it0-f48.google.com with SMTP id m84so23518836ita.0; Tue, 11 Jul 2017 08:02:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-transfer-encoding; bh=HQgfI9UzSTgloUhHsc2aPc4M+halAkKtJQ5I+fVRIyQ=; b=R0xZ4kgrCHpSD1pavvrb5RP6Lk0S6wpYpOYOHRw5PTeWqGd7Ypi8fRC38sGujBiV4x 47Xg4XekLrYGVIkoiLdPtgDy0XA18Z4L+ABXwGxuHhgJyVBe125rhI0l5GrjCH+DTdi7 C9rZNys7/NPjVNGyEf6NKfqYKUiC+nu0bdyPkYiX/fkXnSLWGM/if/js6owjUD9R1YVX mMAbTen3oj5RJR/sLoYQ2odAv4DYzi1VUuzYorSzSmK4FJtdnDae7/vShguRhytCPTLd rHXL5oIseFvCsPI+BazssRnoRkD3K04v5TSGKQo5FX8RuJuf8uVJYTgzBs7Q4us6IfIP 2IFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-transfer-encoding; bh=HQgfI9UzSTgloUhHsc2aPc4M+halAkKtJQ5I+fVRIyQ=; b=E+bc6sa72v8yZRedkf3TvkJPQruaI/O4WUamw5Y6YLTWhnpQszEnaqXz8BOGIkror7 MIFFAat18Isl3rt87fEEWzezjDdgB0DSsDMTJksoh/cGEIQQKNNeBGgBB0Di2cdB4tFX UhR5V0qqXm/iwtCOX+Sc9h7B+AcRKhoG0NzpRVe5McOy/If6RxZaVvTEmYKa5GTNphDb ngAB8wqU/1aLSm5Z4JSijxvtXFwNg6+O8LK6UWru5mefjTrnHHHhLSjB4VXALzjSV2Ax YXNfEdnuuQwRPYlDPHjCHOv0aX7tLTKXsSENyaoS7P63G3eRfvEOFBIYoW5mS4r9GSy7 RW9Q== X-Gm-Message-State: AIVw112mPvJaK56roFRi7psU6Iz9DgULtnLATauYWLYghFW1uj8sQkwE rkvOpDouzjlqBGfAAtD+wA6pyy+XYbtI X-Received: by 10.36.196.67 with SMTP id v64mr3708128itf.89.1499785273918; Tue, 11 Jul 2017 08:01:13 -0700 (PDT) Original-Received: by 10.79.128.213 with HTTP; Tue, 11 Jul 2017 08:00:53 -0700 (PDT) In-Reply-To: X-Google-Sender-Auth: 4C2DkTzKCyT7K6tK6bgbvmR5hzI X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 209.85.214.48 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:216479 Archived-At: On Tue, Jul 11, 2017 at 6:45 PM, Richard Stallman wrote: > I see a misunderstanding. This is not a question of "dealing with" > individual packages one by one. The goal is to make sure people are > aware of the importance of getting legal papers as they accept > contributions. I=E2=80=99d like to voice several ideas related to attracting users and developers and raising awareness of the Emacs contribution policy. 1. Emacs has a web site at . At the same time, the emacs.org domain name, although under control of FSF, stands unused. **Suggestion:** Make https://emacs.org/ the official site of Emacs. Or at least set up redirection from ^https://emacs\.org/\(.*\)$ to https://www.gnu.org/software/emacs/\1. 2. The Emacs web site has a two-line menu, but no =E2=80=9CContributing=E2= =80=9D item in that menu. One has to go through =E2=80=9CDocumentation & Support=E2=80= =9D, then the Reporting Bugs subheading, then actually read the first paragraph of that section, which sends them to the CONTRIBUTE file, which is a literal plain text copy of that file from the source tree. That file goes on to tell a lot of technical things about the development process, but does not mention copyright assignment paperwork except in passing in the section about commit messages. **Suggestions:** * Add an actual =E2=80=9CContributing=E2=80=9D page to the Emacs web site, = and a link to that page to the site menu. * That page should be an attractively formatted web page, not a plain text file with Org markup. * It should be reasonably short, have clear structure, and might link to sub-pages for detailed explanations. * Copyright assignment should be discussed early in that page. It should explain the benefit of copyright assignment concisely, convincingly, and *in terms of the contributor*. (As in, =E2=80=9CIf you assign copyright to us, we will defend it on your behalf against evil corporations that are out there to parasitize on your work=E2=80=9D.) Alternatives should also be explored, with explanations how choosing a different path is bad for *the contributor* as well as the community. 3. The ELPA site, , says this near the bottom of the home page: =E2=80=9CTo contribute new packages refer to the README=E2= =80=9D, where README is a link to another Org-like plain text file that discusses technicalities without mentioning copyright paperwork. **Suggestions:** * Make that README an attractively formatted, well-structured web page or a collection of pages. * Explain copyright assignment and alternatives there, too. 4. The MELPA site is not your competitor. It is there to fill a need, both for users and package authors. **Suggestion:** Place a short notice there, to the effect of =E2=80=9CWould= n=E2=80=99t it be great if your package were accepted into ELPA? Consider this=E2=80=A6= =E2=80=9D with a short explanation of the prerequisites and a link to the ELPA site.