From: Yoni Rabkin <yoni@rabkins.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: ndame@protonmail.com, emacs-devel@gnu.org
Subject: Re: "Write a new package" culture instead of patches?
Date: Mon, 18 May 2020 11:22:47 -0400 [thread overview]
Message-ID: <87v9ktb73s.fsf@rabkins.net> (raw)
In-Reply-To: <83blml9u2t.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 18 May 2020 17:49:30 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> 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.
Rules can be a good thing.
I'm the maintainer of GNU/Emms (a media player for Emacs). The people
who distribute Emms on MELPA do a poor job of it (see below), and have
never communicated with us, the Emms developers about it (not even
once). I only discovered about it by chance recently when I went out to
figure out what M/ELPA is, and how I can add Emms to ELPA.
What the MEPLA people are doing that I don't like:
* Never communicate with the developers of the Emms in any way.
* Omit many files that come with Emms.
* Associate Emms with several Emms extensions that live only on
MELPA and that we, the Emms developers, have never heard
about. This would give anyone accessing Emms via MELPA that those
extensions are somehow a part of Emms, when they are not.
Maybe those extensions are good, in which case I would love for
the developers to contact us, the Emms developers. But Maybe those
extensions are bad, don't work, are out of date, or connect with
non-free services.
* Not even linking to the Emms home page
(https://www.gnu.org/software/emms/).
Thought and effort goes into packaging each version Emms, and presenting
Emms in the best way. It is a shame to see it ignored by this
distribution system.
Ideas for improvement:
* Encourage people to speak to the developers of a project before
packaging it.
* Find a way of packaging a project as-is. For instance, Emms could
be distributed as is, and the M/ELPA software could simply point
at where Emms keeps its .el files for Emacs to find. This is
instead of how I see ELPA working now, which is to force the
software through a kind of a sieve (I think ELPA calls it a
recipe) where only a select few files come out the other end.
Emms doesn't need a recipe; it already comes organized and
packaged for working with Emacs.
It makes me think of taking bread, crumbling it up, the mushing
those crumbs back together to re-form a new loaf of bread.
--
"Cut your own wood and it will warm you twice"
next prev parent reply other threads:[~2020-05-18 15:22 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 [this message]
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
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v9ktb73s.fsf@rabkins.net \
--to=yoni@rabkins.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=ndame@protonmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).