all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: Artur Malabarba <bruce.connor.am@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: ELPA contributions?
Date: Sat, 10 Oct 2015 09:00:47 +0200	[thread overview]
Message-ID: <874mhzi4ww.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CAAdUY-JzV9OTLOnrCOkqNr1RMd963bwCK_Uk-r1JhJ9e65Y3Tw@mail.gmail.com> (Artur Malabarba's message of "Fri, 9 Oct 2015 23:42:27 +0100")

Artur Malabarba <bruce.connor.am@gmail.com> writes:

> The takeaway message is: Yes the readme could use some improvements.
>
> On 9 Oct 2015 9:32 am, "David Kastrup" <dak@gnu.org> wrote:
>> I've taken a look at elpa.gnu.org and the README referenced in there,
>> and at lists.gnu.org.  There does not appear to be a discussion list for
>> ELPA,
>
> There isn't. Elpa stuff is discussed on the emacs lists. But the Readme
> should certainly say that.
>
>> and the README just contains the technical details of uploading
>> material to ELPA (it's not really clear when to choose an external
>> branch).
>
> Yes, that needs to be clarified too. The idea is to just use a subtree,
> unless you _know_ you want an external branch for some reason.
>
>> 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.  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".

And if I don't hear anything about the prospected file/project I posted
here, that's likely what I'll end up doing.

Still feels a bit unsual, though.

-- 
David Kastrup



  parent reply	other threads:[~2015-10-10  7:00 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 [this message]
2015-10-10 22:24     ` Artur Malabarba
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=874mhzi4ww.fsf@fencepost.gnu.org \
    --to=dak@gnu.org \
    --cc=bruce.connor.am@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 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.