From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Michelangelo Rodriguez Newsgroups: gmane.emacs.devel Subject: Re: Package proposal: greader, an audio emacs reader for blind and dislexic people Date: Thu, 31 Jan 2019 07:04:43 +0100 (CET) Message-ID: References: <87tvhpx0fr.fsf@web.de> <87ftt9wpfh.fsf@web.de> <965f7e5c3c7be56ae4c6141eabe13d8a@webmail.orcon.net.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="235803"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Alpine 2.21 (DEB 202 2017-01-01) To: emacs devel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 31 07:05:01 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gp5TB-000zDA-03 for ged-emacs-devel@m.gmane.org; Thu, 31 Jan 2019 07:05:01 +0100 Original-Received: from localhost ([127.0.0.1]:49326 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gp5T9-00049K-VI for ged-emacs-devel@m.gmane.org; Thu, 31 Jan 2019 01:05:00 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:51141) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gp5T0-00048z-RX for emacs-devel@gnu.org; Thu, 31 Jan 2019 01:04:51 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gp5Sz-0006Mi-So for emacs-devel@gnu.org; Thu, 31 Jan 2019 01:04:50 -0500 Original-Received: from mail-wm1-x341.google.com ([2a00:1450:4864:20::341]:39841) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gp5Sz-0006Ka-Mi for emacs-devel@gnu.org; Thu, 31 Jan 2019 01:04:49 -0500 Original-Received: by mail-wm1-x341.google.com with SMTP id y8so1155741wmi.4 for ; Wed, 30 Jan 2019 22:04:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:in-reply-to:message-id:references:user-agent :mime-version; bh=UxEIAqQxmC9qPLJEzhHAtgIZ7Eu5F0f8jtEzYNkc1bY=; b=sOktkbG784yjl+PxXYDOaspmApYAzZF1YL02uFo4sUMOyKeUBwL7sR1Hi6dQmk5b7R 6goJX1fh6r4eRY8RYa/YXyzTqQtm6h2KAK9hLLqpR5BM3tTjmZTpmJQ+Vq5Y21tYcQF+ mSLlwn92E+MfqngXawazIqt7mspVgAv/4nRed85YjSXXe2XtlLeFZ8HeDKQfadfxMSCl x2XMFkiK3EnDPOuYI7q6XpJQEj+fX62WuovdicTB35rZNzZfeZ29vvrddylEGjmKZKPF p0p9kV6TI6Bic/SvzG6v2XnCEfKI2AJmUZYyf+m5QbmmU15fl26NfUiPsyMMo84FwXRR gjSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:in-reply-to:message-id :references:user-agent:mime-version; bh=UxEIAqQxmC9qPLJEzhHAtgIZ7Eu5F0f8jtEzYNkc1bY=; b=gF925MKydJsKKnj+rqBu4kI+pRyY5RN1MqSGkWpRlIeycEUhzoToU5ybreb3xj1fdK 3vbOPYOoc3PLl2Eh0U/ynBTV4jLB/RdRT19V1cNdwHyiu2AaySdoxP+BOTHiZZs0Ykbl o0zvJFPICPaE+mZHQ/gjP6QVsmm0GdoBh98LnXke7O40zCSbM7B8j6U7rQ0ArmGM4ISk serXHnE2O5YJX7IfJz3qboD6n3mMyYDkS9tnDLZoRpJ+dlVhRDLoCVNyjJndPEYnYu4X cDBiULMJXxKBwFuMqlVdo8CY07lRyU2BuTVCLvm1OPmYFIbizsQQnnBaclurkNX59LEb Skfg== X-Gm-Message-State: AJcUukcqvCxdzayen/Pww4IvDd2bJzuiEhw4WV2Wo/FQjZlv60lPm5ky rXiUu3uzCkgYtEkHvdtCeZUL5j92 X-Google-Smtp-Source: ALg8bN50TXSZ8lUWBJxbqcmCm1csWliAkBBIva2q6IBTYgG3ejrzKLjjrYCfzna32U+tvDYpVmZg4w== X-Received: by 2002:a1c:1a43:: with SMTP id a64mr26734876wma.136.1548914685004; Wed, 30 Jan 2019 22:04:45 -0800 (PST) Original-Received: from mugno.homenet.telecomitalia.it (host235-210-dynamic.13-79-r.retail.telecomitalia.it. [79.13.210.235]) by smtp.gmail.com with ESMTPSA id k23sm2954955wmj.32.2019.01.30.22.04.44 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 30 Jan 2019 22:04:44 -0800 (PST) X-X-Sender: michelangelo@mugno.localdomain In-Reply-To: <965f7e5c3c7be56ae4c6141eabe13d8a@webmail.orcon.net.nz> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1450:4864:20::341 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:232850 Archived-At: Where i can find information about how to adere at the gnu standards?i'm sorry for my perhaps trivial question, but i'm newbie in emacs development and, at the same time, i want to start to contribute to the community. in a consistent way. Thanks in advance. On Thu, 31 Jan 2019, Phil Sainty wrote: > On 2019-01-31 16:13, Tim Cross wrote: >> The thing about GNU ELPA is that all the packages in there are >> actively maintained and kept up to date with current version of Emacs. >> The mor packages in there, the more work is required to release new >> versions of Emacs. > > I don't believe that's the case at all. > > GNU ELPA packages are not part of core Emacs, and anyone can contribute > them (within the FSF rules). If new Emacs releases might be held back > on account of any arbitrary ELPA package not working, this is the first > I've heard of it. Maybe certain packages which are considered > particularly important might have such status in effect, and obviously > if bugs are reported against ELPA packages then they could be fixed, > but I don't think adding ELPA packages increases the amount of work > required to release new versions of Emacs? > > After all, one of the acknowledged advantages of ELPA packages is that > they can be updated outside of Emacs release cycles, so it is *less* > important that ELPA bugs be fixed prior to an Emacs release, because > they can be fixed afterwards without the need of another Emacs release. > > >> IMO the GNU ELPA repository is really for packages that represent >> core Emacs functionality. For non-core things, we have MELPA, which >> sounds like a better fit for this package. > > Definitely not true. GNU ELPA and MELPA are simply two instances of > package archives. There are plenty of packages in GNU ELPA which are > nothing like "core" functionality, and plenty of packages in MELPA > that I wish had been contributed to either GNU ELPA or Emacs core. > It's not the case that the two archives were established for the > purposes you've described. The only distinction I draw between them > is that one requires contributors to follow the FSF rules, and the > other does not. > > >> Regardless, I think the better approach is to first develop and >> release the package in MELPA. If it becomes popular and the community >> believes it would be a good fit for GNU ELPA, it can be moved over to >> that repository. > > That can be a recipe for failure. Too many packages get contributed > to MELPA, get popular, and then *can't* be "moved over" to GNU ELPA > because the author wasn't taking care of the copyright issue while it > was on MELPA, and suddenly finds that they've accepted code contributions > into their package which are blocking that move. The more popular the > package becomes, the more likely that situation is to occur. It's > better to start in GNU ELPA and ensure that this problem is avoided > from the outset. > > (There's a LOT of good elisp out there which would benefit Emacs core, > but which will never do so because by the time it was "good enough" for > that to happen, it was also completely impractical to assign the copyright > to the FSF.) > > > -Phil >