From: Eli Zaretskii <eliz@gnu.org>
To: ndame <ndame@protonmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: "Write a new package" culture instead of patches?
Date: Sun, 17 May 2020 22:33:27 +0300 [thread overview]
Message-ID: <83tv0e9x14.fsf@gnu.org> (raw)
In-Reply-To: <C_DXd2k5pICkZfOIWhiwsEM0waQCb4M_TRsBkiL9-ytPjHOwo2jDeuYEWrg6nuZ6Z0suiqYCYWnGRdiF6qmSgYF5eYTmykkN6EW0adXVwZU=@protonmail.com> (message from ndame on Sun, 17 May 2020 19:25:50 +0000)
> Date: Sun, 17 May 2020 19:25:50 +0000
> From: ndame <ndame@protonmail.com>
>
> The obvious answer is because they solved the problem, it works, available to anyone and they can't be
> bothered with jumping through additional hoops (paperwork, following the core rules for docs, code
> formatting, commit message, etc.).
>
> For some people getting their code into the core is a source of pride. For others it's a pointless excercise,
> because it's trivially available from MELPA which the majority of users use anyway for other packages too.
But MELPA asks you to jump through a different set of hoops, which
seems to fly in the face of your theory.
IME, many people who "solved the problem" want others to enjoy their
solution, and that is what gives them the incentive to "jump through
hoops".
next prev parent reply other threads:[~2020-05-17 19:33 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 [this message]
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
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=83tv0e9x14.fsf@gnu.org \
--to=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 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.