From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Artur Malabarba Newsgroups: gmane.emacs.devel Subject: [ELPA] Proposed (small) rules change Date: Wed, 14 Oct 2015 13:59:43 +0100 Message-ID: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1444827721 4774 80.91.229.3 (14 Oct 2015 13:02:01 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 14 Oct 2015 13:02:01 +0000 (UTC) To: emacs-devel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Oct 14 15:02:00 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZmLgq-0000uz-4m for ged-emacs-devel@m.gmane.org; Wed, 14 Oct 2015 15:01:56 +0200 Original-Received: from localhost ([::1]:42204 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZmLgp-0004Cj-I3 for ged-emacs-devel@m.gmane.org; Wed, 14 Oct 2015 09:01:55 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:51438) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZmLek-0002XT-Ed for emacs-devel@gnu.org; Wed, 14 Oct 2015 08:59:47 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZmLei-0004hu-Po for emacs-devel@gnu.org; Wed, 14 Oct 2015 08:59:46 -0400 Original-Received: from mail-lf0-x236.google.com ([2a00:1450:4010:c07::236]:36157) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZmLei-0004hk-Ix for emacs-devel@gnu.org; Wed, 14 Oct 2015 08:59:44 -0400 Original-Received: by lfeh64 with SMTP id h64so10855961lfe.3 for ; Wed, 14 Oct 2015 05:59:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=bFHPrybeEdBNLHIBVMRpN1Bi0C8wukmB2EySknKXk0k=; b=OZ1eRRNv0Qqpo32lNriO24sffg7YaOCzYyslTIhEltw2DG5y/zchq16x6MIbb39h4q VcLoOY53WbpWB4OV7FhN80i05h6J5kFau/OZDNielY1kxVB7Awn1/r2dGhfhktFtqpjH 5/14h8IrYxah6bYpj7rsn2ZNnWk3XBXAqJSzD/ZpOi0Ys9sriaQvF3H6CInDYtrfrRQe KL9TvL4EZBoyZzisNztFsM46Gu5DtDRzQwcPnBSNbZslxZItTYsvyhAtOMvRt1/rD12g q/O/zuIJRnN81V4Mdn2qZRUdQAbPVHD7o0RR+ArqwW5DeeRxoF0x3qKggYCu2YTaY3pP TF8w== X-Received: by 10.25.210.206 with SMTP id j197mr1021821lfg.86.1444827583781; Wed, 14 Oct 2015 05:59:43 -0700 (PDT) Original-Received: by 10.25.22.197 with HTTP; Wed, 14 Oct 2015 05:59:43 -0700 (PDT) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4010:c07::236 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:191557 Archived-At: I'd like to make the following change to Elpa's Readme. It asks that people send an email to emacs-devel before adding any package (which is something that most already do anyway, though I'm guilty of the contrary). This is not intended to scare away new contributors. It is actually intended to make them feel safer that someone is actually checking what they're about to do. Cheers, Artur Malabarba --- * README: Add submission guideline 1 file changed, 30 insertions(+), 1 deletion(-) README | 31 ++++++++++++++++++++++++++++++- modified README @@ -34,7 +34,36 @@ safely work on the next version here without worrying about the unstable code making it to GNU ELPA, and simply update the "version" when you want to release the new code. -** To add a package: +** To add a package: (submission, submit) + +*** Notify emacs-devel@gnu.org + +There is no approval process for GNU Elpa packages. Still, +you must send an email to emacs-devel for several reasons: + +- Notifying other developers; +- Making sure the package doesn't break FSF rules; +- Checking if the package is not reinventing the wheel; +- Ensuring that first-time developers are doing it right. + +Send an email to the list with the subject: + [ELPA] New package: + +Start your message with an explanation about the package. A +copy-paste of the package's Summary and Commentary is perfectly fine +here. + +At the bottom of the message contents include the changes you're going +to make (the patch). For a single-file package this can also be the +package file itself. If you prefer, you can push your changes to a +branch called `scratch/', and mention the branch in your +message. + +After 48h, if nobody points out any issues, feel free to push your +commits. You should probably also subscribe to emacs-devel@gnu.org, +since that's where we discuss about GNU Elpa, and to +bug-gnu-emacs@gnu.org, since that's where people will report bugs +about your package. *** Add a simple (1-file) package as packages//.el.