all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: phillip.lord@russet.org.uk (Phillip Lord)
Cc: emacs-devel@gnu.org
Subject: Re: In Support of ELPA
Date: Thu, 13 Jul 2017 22:12:38 -0400	[thread overview]
Message-ID: <jwv60evdb3p.fsf-monnier+Inbox@gnu.org> (raw)
In-Reply-To: <87wp7ccnz6.fsf@russet.org.uk> (Phillip Lord's message of "Thu, 13 Jul 2017 17:15:25 +0100")

> 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.

"The outside host" is a machine, it's not a "someone".
"has write access" is a property which can change over time.  So unless
we have some process or someone watching over those changes "had write
access when we added the package" will often turn into some rather
irrelevant historical data,

> 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.

"git push elpa" is not that hard either.


        Stefan



  parent reply	other threads:[~2017-07-14  2:12 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
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 [this message]
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=jwv60evdb3p.fsf-monnier+Inbox@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=phillip.lord@russet.org.uk \
    /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.