all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: "Write a new package" culture instead of patches?
Date: Mon, 18 May 2020 11:57:28 -0400	[thread overview]
Message-ID: <b891f7e3-b222-d4d6-3a20-42a2f3af4437@gmail.com> (raw)
In-Reply-To: <83blml9u2t.fsf@gnu.org>

On 18/05/2020 10.49, Eli Zaretskii wrote:
>> From: Philippe Vaucher <philippe.vaucher@gmail.com>
>> Date: Mon, 18 May 2020 07:41:42 +0200
>> Cc: Eli Zaretskii <eliz@gnu.org>, "emacs-devel@gnu.org" <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.



  parent reply	other threads:[~2020-05-18 15:57 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-17 19:25 "Write a new package" culture instead of patches? ndame
2020-05-17 19:33 ` Eli Zaretskii
2020-05-17 19:43   ` ndame
2020-05-18  2:22     ` Eli Zaretskii
2020-05-17 19:48   ` Arthur Miller
2020-05-17 19:58   ` ndame
2020-05-18  5:41     ` Philippe Vaucher
2020-05-18 14:49       ` Eli Zaretskii
2020-05-18 15:22         ` Yoni Rabkin
2020-05-18 16:33           ` Clément Pit-Claudel
2020-05-18 17:30             ` Yoni Rabkin
2020-05-18 17:50               ` Dmitry Gutov
2020-05-18 19:17                 ` Clément Pit-Claudel
2020-05-18 19:31                   ` Dmitry Gutov
2020-05-18 20:13                 ` Yoni Rabkin
2020-05-18 21:23                   ` Dmitry Gutov
2020-05-18 19:35               ` Clément Pit-Claudel
2020-05-18 20:17                 ` Yoni Rabkin
2020-05-18 20:38                   ` Clément Pit-Claudel
2020-05-20  4:01                   ` Clément Pit-Claudel
2020-05-18 21:12                 ` Stefan Monnier
2020-05-18 15:57         ` Clément Pit-Claudel [this message]
2020-05-18 16:22           ` Stefan Kangas
  -- strict thread matches above, loose matches on Subject: below --
2020-05-11 16:41 dash.el [was: Re: Imports / inclusion of s.el into Emacs] Alfred M. Szmidt
2020-05-11 17:12 ` 조성빈
2020-05-12  3:16   ` Richard Stallman
2020-05-12  3:55     ` Stefan Monnier
2020-05-13  3:57       ` Richard Stallman
2020-05-13 12:27         ` Stefan Monnier
2020-05-14  5:10           ` Richard Stallman
2020-05-14 13:44             ` Stefan Monnier
2020-05-17  2:53               ` Richard Stallman
2020-05-17 13:01                 ` Eli Zaretskii
2020-05-17 13:38                   ` Dmitry Gutov
2020-05-17 14:24                     ` Eli Zaretskii
2020-05-17 18:27                       ` Dmitry Gutov
2020-05-17 18:52                         ` "Write a new package" culture instead of patches? Stefan Kangas
2020-05-17 19:42                           ` Dmitry Gutov
2020-05-17 22:14                             ` Yuan Fu
2020-05-17 22:44                               ` Arthur Miller
2020-05-17 23:13                               ` chad
2020-05-17 23:22                                 ` Stefan Monnier
2020-05-18  1:31                                   ` João Távora
2020-05-18  1:55                                   ` Tim Cross
2020-05-19  3:51                                   ` Richard Stallman
2020-05-19  3:51                               ` Richard Stallman
2020-05-19  4:33                                 ` Stefan Kangas
2020-05-17 21:14                           ` Alan Third
2020-05-17 22:02                             ` Arthur Miller
2020-05-18  7:58                               ` tomas
2020-05-18 12:08                                 ` Arthur Miller
2020-05-18 12:26                                   ` tomas
2020-05-18 23:07                                     ` arthur miller
2020-05-19  7:27                                       ` tomas
2020-05-17 21:51                           ` Matthias Meulien

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b891f7e3-b222-d4d6-3a20-42a2f3af4437@gmail.com \
    --to=cpitclaudel@gmail.com \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.