all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: ELPA update
Date: Wed, 28 Sep 2011 08:52:04 -0500	[thread overview]
Message-ID: <87wrcsrczf.fsf@lifelogs.com> (raw)
In-Reply-To: 87ehz1ds54.fsf@keller.adm.naquadah.org

On Wed, 28 Sep 2011 09:48:23 +0200 Julien Danjou <julien@danjou.info> wrote: 

JD> On Tue, Sep 27 2011, Chong Yidong wrote:

>> It seemed preferable to have some human component in the procedure of
>> rolling out packages to users.  For instance, I try to scan the bzr logs
>> before doing each update.
>> 
>> But I'm open to arguments for simply setting it up as a cron job.

JD> I hope that the checks are done before commiting. :-) So I'd rather like
JD> a daily cronjob rathen than disturbing you each time I commit a bugfix
JD> that I want to give to users.
JD> And as the number of package will increase, I'm not sure you'll be able
JD> to do this review manually so, it might be best to trust us on short
JD> term. :)

I think the GNU ELPA is much more like a package repository than a
source code repository, so it makes sense to have some human overview,
especially considering the large number of committers.  We don't want
rogue code sneaking in and compromising our users.

To that end it would also be nice if we asked committers to sign their
contributions with their private GPG key, but I don't know if Bazaar
supports that.  If they did, we could have a list of approved public GPG
keys for any given package and contributions signed with those could be
automatically approved.  This is just a proposal though, I don't know
the best way to do it.

Most of us don't know how to run a package repository, so maybe we
should look at the Debian maintainers' process or ask them if we don't
have the local expertise.

Ted




  parent reply	other threads:[~2011-09-28 13:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-27 14:25 ELPA update Julien Danjou
2011-09-27 15:53 ` Chong Yidong
2011-09-28  7:48   ` Julien Danjou
2011-09-28  8:41     ` Tassilo Horn
2011-09-28 14:05       ` Stefan Monnier
2011-09-28 17:30         ` Ted Zlatanov
2011-10-12  4:58           ` Stefan Monnier
2011-09-28 13:52     ` Ted Zlatanov [this message]
2011-09-28 14:00       ` Julien Danjou
2011-09-28 17:25         ` Ted Zlatanov
2011-09-28 17:28           ` Julien Danjou
2011-09-28 18:43             ` Ted Zlatanov
2011-09-28 20:58             ` Stefan Monnier
2011-09-28 23:01               ` PJ Weisberg
2011-09-29  1:16                 ` Stephen J. Turnbull
2011-09-29  8:45                   ` Ted Zlatanov
2011-09-29 10:14                     ` Julien Danjou
2011-09-29 12:36                       ` Ted Zlatanov
2011-09-29 14:09                         ` Julien Danjou
2011-09-29 15:08                           ` Ted Zlatanov
2011-09-29 12:26                     ` Stephen J. Turnbull
2011-09-28 14:53       ` Eli Zaretskii
2011-09-29  7:43 ` Jambunathan K
2011-09-29 15:03   ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wrcsrczf.fsf@lifelogs.com \
    --to=tzz@lifelogs.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.