From: Artur Malabarba <bruce.connor.am@gmail.com>
To: David Kastrup <dak@gnu.org>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: ELPA contributions?
Date: Sat, 10 Oct 2015 23:24:43 +0100 [thread overview]
Message-ID: <CAAdUY-L+atthRUpa4NdJHYnMvzBCMdD4s5xCCss=Ad7xzZiVdA@mail.gmail.com> (raw)
In-Reply-To: <874mhzi4ww.fsf@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]
On 10 Oct 2015 8:00 am, "David Kastrup" <dak@gnu.org> wrote:
> >> There are no obvious submission addresses or anything like
> >> that.
> >
> > Yes, that should just be Emacs-devel as well.
>
> That does not really appear to match the realities. There are a host of
> commits in ELPA coming from known Emacs developers (well, push
> access...) for projects I never heard of on the developer list.
There's no enforced submission process yet. But if you want to submit a
package for consideration (because you're new or you don't know if it's
worth it) then emacs-devel is the place. That's the current reality.
> And
> since ELPA contributions (if I understood correctly) require an Emacs
> copyright assignment anyway and that is coupled with commit access
> fairly often, there really is a strong appearance of "just write to ELPA
> if you think you know what you are doing".
Pretty much. Yes, it's unusual. I suppose the number of contributors has
been small, so it's worked so far (but I'm fairly new here so it's just my
impression).
We could require that people send new packages to emacs-devel before
pushing them. These wouldn't be used to veto/approve packages, it would
most be an announcement/feedback-request/ensure-it-doesnt-violate-fsf-rules
thing.
- if we're going to enforce a submission
[-- Attachment #2: Type: text/html, Size: 1657 bytes --]
next prev parent reply other threads:[~2015-10-10 22:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 8:32 ELPA contributions? David Kastrup
2015-10-09 22:42 ` Artur Malabarba
2015-10-10 6:55 ` David Kastrup
2015-10-10 7:00 ` David Kastrup
2015-10-10 22:24 ` Artur Malabarba [this message]
2015-10-10 22:26 ` Artur Malabarba
2015-10-12 12:44 ` Phillip Lord
2015-10-12 16:00 ` Eric Abrahamsen
2015-10-12 20:54 ` Phillip Lord
2015-10-12 21:54 ` Artur Malabarba
2015-10-13 9:27 ` Phillip Lord
2015-10-12 21:25 ` Artur Malabarba
2015-10-12 22:14 ` Eric Abrahamsen
2015-10-12 22:32 ` Eric Abrahamsen
2015-10-13 9:35 ` Phillip Lord
2015-10-13 11:30 ` Artur Malabarba
2015-10-13 17:38 ` Eric Abrahamsen
2015-10-14 11:14 ` Phillip Lord
2015-10-12 21:44 ` Artur Malabarba
2015-10-13 11:15 ` Phillip Lord
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='CAAdUY-L+atthRUpa4NdJHYnMvzBCMdD4s5xCCss=Ad7xzZiVdA@mail.gmail.com' \
--to=bruce.connor.am@gmail.com \
--cc=dak@gnu.org \
--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.