From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: =?UTF-8?Q?Cl=c3=a9ment_Pit-Claudel?= Newsgroups: gmane.emacs.devel Subject: Re: "Write a new package" culture instead of patches? Date: Mon, 18 May 2020 11:57:28 -0400 Message-ID: References: <83tv0e9x14.fsf@gnu.org> <83blml9u2t.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="129812"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon May 18 17:58:43 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jaiA6-000Xf2-9h for ged-emacs-devel@m.gmane-mx.org; Mon, 18 May 2020 17:58:42 +0200 Original-Received: from localhost ([::1]:59456 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jaiA5-0005WO-7q for ged-emacs-devel@m.gmane-mx.org; Mon, 18 May 2020 11:58:41 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53134) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jai8y-0003lr-M0 for emacs-devel@gnu.org; Mon, 18 May 2020 11:57:32 -0400 Original-Received: from mail-qk1-x735.google.com ([2607:f8b0:4864:20::735]:40306) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jai8x-00012N-PV for emacs-devel@gnu.org; Mon, 18 May 2020 11:57:32 -0400 Original-Received: by mail-qk1-x735.google.com with SMTP id g185so10561543qke.7 for ; Mon, 18 May 2020 08:57:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=1aytfnOSt68ahlxGA1pKRnSxFq/rV7srJbBY5OgdYbc=; b=RKlx2c5zqKHkgJM0yf+TEW4XGbI2bzcdj+5VkYOI0qDIHuJC00yrf0EVLY96NUn11V bp82RV3KChcNjmcxOYnoUOoCXhUnA6xOT91UIvjieoxbLT+tOCCgIhdyVBLxLn2KBodC bwXnLhHz1oqrU0W0Exrv5zTPkucMBcXIgbV6lzuY/LI3QNrjQxbX0aaUNL+PuE7m8nBw l2Th7Btdny+Br0uRbSEnhMQL5QQpEw/re4FJL274OWpD5QImSkKPcU0KeVpMavd73blu IOAmeEWQcvnlukOOi0n+NTa5J7Zhtgp22l+2HjrY48m2NRJ2EK4EW0u4Etsqkmgxj/22 NkGA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=1aytfnOSt68ahlxGA1pKRnSxFq/rV7srJbBY5OgdYbc=; b=GHjUpvCKE/3fcY9bLFTEoy4HG17pPd9CiOVgGJTPczK4XJyz9ceF1PfddY/YqI14sW 6G6H+H8KJRC86koMRuUQWg2LuBgpGuBlx3B/ZH7bRTFVKHXodTpKFkBb0etk7ntnUtz7 8BVcRpQv+oShuNjtAmjxc4Gef9fl9JMWSo+iVMSkaaOkVA7C9Dq7YI4CxVelLWYlu9en i62XNJ7FYD7loEkLBCGU8OuLcAWEQdtlYGEIlaYUxst6LvH8YYt0ZPao9rRMO1gkKEB6 NfVbqph4Wp3iwDyViS9MDvMy4OrZgNJFkNoev6PofmN71FJfPLKlNcsCjGSfcjZ/jaeR M5Ug== X-Gm-Message-State: AOAM530skQi/Qb2CPnAl+feCVNYpskFTq0D3iSRnNTMeezNrrv88zzDq LvBHsWee9nTAJ6i9jcOsR0lWswN/ X-Google-Smtp-Source: ABdhPJwks0A6gI4tbZ0DemU8xQA2atlipxnucPqpNTsTfs+J3DZa16aqq3YrKN4QVZPVYdQ5Yrejyw== X-Received: by 2002:a37:7105:: with SMTP id m5mr17188774qkc.370.1589817450584; Mon, 18 May 2020 08:57:30 -0700 (PDT) Original-Received: from ?IPv6:2601:184:4180:66e7:bda5:ac5c:1de0:b677? ([2601:184:4180:66e7:bda5:ac5c:1de0:b677]) by smtp.googlemail.com with ESMTPSA id u56sm9872727qtb.91.2020.05.18.08.57.29 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 18 May 2020 08:57:30 -0700 (PDT) In-Reply-To: <83blml9u2t.fsf@gnu.org> Content-Language: en-GB Received-SPF: pass client-ip=2607:f8b0:4864:20::735; envelope-from=cpitclaudel@gmail.com; helo=mail-qk1-x735.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:250766 Archived-At: On 18/05/2020 10.49, Eli Zaretskii wrote: >> From: Philippe Vaucher >> Date: Mon, 18 May 2020 07:41:42 +0200 >> Cc: Eli Zaretskii , "emacs-devel@gnu.org" >> >> That said, for those living on github/gitlab/etc compared to ELPA you >> feel at home... you just open issues, make pull requests & get >> answered there, you feel "welcome". On ELPA/emacs-devel you don't feel >> as welcome because of copyright assignments / subscribing to a mailing >> list / having to create patches and send an email, that plus usually >> the first answer you receive is that you did your commit message all >> wrong and that it follows complex rules in a tone that is more serious >> and "hard work" than what you get on MELPA. > > I think you make the MELPA rules sound easier, and our rules sound > harder, than they actually are. I suggest to scan the archives for > proposals to add new packages to ELPA, where you will see neither the > need to subscribe to this list, nor the need to create patches and > email them, nor "all wrong" responses with a certain "tone". At least > not in general. Part of the problem could be perception? MELPA does an incredible job at explaining the process to get accepted (and indeed they get slightly more than one new package per day). To address this, what about (1) adding a prominent link to elpa.gnu.org on www.gnu.org/software/emacs, and (2) on elpa.gnu.org, removing "To contribute a new package refer to the README" and replacing it with a new section titled "Contributing packages"? That section would include the part of the README that deals with new packages, and would highlight external branches more prominently, since those are closer to MELPA's way of doing things. How does pushing to these branches work, btw? Do we have a way on savannah to give a user push access to a single branch? Or do we give savannah access to everyone who submits a package? Clément.