[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ELPA policy
From: |
Chong Yidong |
Subject: |
Re: ELPA policy |
Date: |
Mon, 15 Nov 2010 15:12:15 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) |
Stefan Monnier <address@hidden> writes:
> For new packages, I'd expect only a few people to have such rights,
> but for updates, I'd expect something like "anybody with access to the
> Bzr repository". After all, if they can screw with the main Emacs
> codebase, why not with the ELPA packages.
One difference, though, is that screwing with the main Emacs codebase
affects only those using the development version of Emacs, and we have
mechanisms like the diffs mailing list for problems to be easily
spotted. After Emacs 24 is released, by screwing with elpa.gnu.org you
can immediately affect users of deployed stable Emacs versions.
So, we need to be a bit more paranoid for elpa.gnu.org than for our main
repository.
I agree, though, that it would be nice for Emacs developers to easily
edit packages in elpa.gnu.org without going through an onerous package
upload process. I'm not sure how to set this up, though maybe the way
the Org daily builds are handled can be used as a starting point.
- Re: elpa.gnu.org policy, (continued)
- Re: elpa.gnu.org policy, Glenn Morris, 2010/11/15
- Re: elpa.gnu.org policy, Lars Magne Ingebrigtsen, 2010/11/16
- compat unification (was: elpa.gnu.org policy), Lars Magne Ingebrigtsen, 2010/11/16
- Re: compat unification, Stefan Monnier, 2010/11/16
- Re: compat unification, Lars Magne Ingebrigtsen, 2010/11/16
- Re: compat unification, Glenn Morris, 2010/11/16
- RE: elpa.gnu.org policy, Drew Adams, 2010/11/16
Re: ELPA policy, Tom Tromey, 2010/11/15
Re: ELPA policy, Stefan Monnier, 2010/11/15
- Re: ELPA policy,
Chong Yidong <=
Re: ELPA policy, Richard Stallman, 2010/11/16