From: Drew Adams <drew.adams@oracle.com>
To: bruce.connor.am@gmail.com, Matthew Leach <matthew@mattleach.net>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: RE: Best practice for sharing new Emacs modules
Date: Mon, 11 Jan 2016 13:43:58 -0800 (PST) [thread overview]
Message-ID: <46ae5c06-92df-424a-8465-7ac9638fbb16@default> (raw)
In-Reply-To: <CAAdUY-JOEyM872kDPQdtG5GK00Tf8unqvKj+h+4OKv1-RgoD=w@mail.gmail.com>
> > I do have one question: what is the best/accepted way to share
> > the code with the Emacs community?
>
> 1. You can send us the .el file and ask to have it included in GNU
> Elpa (this means it will show up for anyone who runs `M-x
> list-packages').
>
> 2. You can push it to Github and then have it included on Melpa (see
> https://github.com/milkypostman/melpa for instructions).
>
> These two options are not mutually exclusive, but they're pretty
> redundant, so I'd recommend just choosing one.
You can also post in on Emacs Wiki, in the Elisp Area:
http://www.emacswiki.org/ElispArea
And then send a message to contact@milkbox.net with a simple recipe
for inclusion in MELPA. MELPA can pick up libraries automatically
(e.g. daily) from GitHub or the wiki. For the wiki, you just need
to provide a recipe.
A "recipe" can be as simple as this, where the part after `;' is
a short description.
(character-fold+ :fetcher wiki) ; Extensions to `character-fold.el'.
If the library includes multiple files then the recipe is a bit
more involved. You can contact contact@milkbox.net for more info.
next prev parent reply other threads:[~2016-01-11 21:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 19:43 Best practice for sharing new Emacs modules Matthew Leach
2016-01-11 20:23 ` Clément Pit--Claudel
2016-01-11 21:22 ` Artur Malabarba
2016-01-11 21:43 ` Drew Adams [this message]
2016-01-11 22:33 ` Clément Pit--Claudel
2016-01-12 0:25 ` John Wiegley
2016-01-12 4:36 ` Stefan Monnier
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=46ae5c06-92df-424a-8465-7ac9638fbb16@default \
--to=drew.adams@oracle.com \
--cc=bruce.connor.am@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=matthew@mattleach.net \
/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).