From: Stefan Kangas <stefankangas@gmail.com>
To: "Clément Pit-Claudel" <cpitclaudel@gmail.com>, emacs-devel@gnu.org
Subject: Re: "Write a new package" culture instead of patches?
Date: Mon, 18 May 2020 09:22:08 -0700 [thread overview]
Message-ID: <CADwFkmncCDvOoeJar7MNU+xtxTD8o9YFmYkgG6reZb_XmdSN=w@mail.gmail.com> (raw)
In-Reply-To: <b891f7e3-b222-d4d6-3a20-42a2f3af4437@gmail.com>
Clément Pit-Claudel <cpitclaudel@gmail.com> writes:
> 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"?
At least (2) would help I think.
But then again, that's assuming that people even visit elpa.gnu.org in
the first place. So maybe (1) is a good idea too.
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2020-05-18 16: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
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 [this message]
-- 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='CADwFkmncCDvOoeJar7MNU+xtxTD8o9YFmYkgG6reZb_XmdSN=w@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=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 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).