From: phillip.lord@russet.org.uk (Phillip Lord)
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: In Support of ELPA
Date: Thu, 13 Jul 2017 17:15:25 +0100 [thread overview]
Message-ID: <87wp7ccnz6.fsf@russet.org.uk> (raw)
In-Reply-To: <jwv8tjuob3w.fsf-monnier+gmane.emacs.devel@gnu.org> (Stefan Monnier's message of "Tue, 11 Jul 2017 18:37:18 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> I think, though, this is still a bit clunky. I think it would be nice to
>> add support for MELPA recipes directly in ELPA. This was adding an MELPA
>> package to ELPA would require simply copying the recipe from MELPA.
>
> I find it is important for GNU ELPA not to *pull* from outside hosts
> that are not under our control. Instead code should be pushed to it by
> people who have write access (hence take on the responsibility of paying
> attention to copyright and such).
If the outside host is someone who has write access to ELPA does it make
any difference? It's just a different way of trusting people.
Ultimately, pull requests of this form would result in emails going to
the ELPA-diffs mailing list, so we'd be able to check there. And, if we
can get the people who have assigned copyright as a CSV along with their
aliases, you could check the commit messages on the way through for
authorship.
Phil
next prev parent reply other threads:[~2017-07-13 16:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 21:46 In Support of ELPA Phillip Lord
2017-07-11 22:37 ` Stefan Monnier
2017-07-12 13:30 ` Ted Zlatanov
2017-07-13 12:23 ` Richard Stallman
2017-07-13 15:05 ` Ted Zlatanov
2017-07-13 22:02 ` Phillip Lord
2017-07-13 16:15 ` Phillip Lord [this message]
2017-07-14 1:20 ` Richard Stallman
2017-07-14 10:02 ` Phillip Lord
2017-07-16 1:50 ` Richard Stallman
2017-07-17 14:05 ` Phillip Lord
2017-07-14 2:12 ` Stefan Monnier
2017-07-14 6:48 ` Thien-Thi Nguyen
2017-07-15 1:35 ` Richard Stallman
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=87wp7ccnz6.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.