emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Scot Becker <scot.becker@gmail.com>
To: Bastien <bastien.guerry@wikimedia.fr>
Cc: emacs-orgmode@gnu.org, Jambunathan K <kjambunathan@gmail.com>
Subject: Re: [WISH] ELPA repo for org-mode?
Date: Wed, 22 Sep 2010 00:07:40 +0100	[thread overview]
Message-ID: <AANLkTikVoHhEoNLRYtQMp4ux9Gb0U7eEQ-C=4mL46+zL@mail.gmail.com> (raw)
In-Reply-To: <87zkva204d.fsf@gnu.org>

> 1) more goes to org-mode/contrib/lisp: this is okay, but requires
>   more people to have write access to Org

I can't comment on whether that is undesirable, but I assume that if
the number of contributions grows, it might be best to take one of the
other routes.

> 2) have a separate Org contribs repo: then we can be more liberal
>   with write access and let users have all extensions in one pull.

This would be find with me.  Git is easy and quick.

> 3) migrate as much Org extensions as possible to ELPA: I'm still
>   trying to figure out what would be the consequences of this.

Well, for one thing, at the moment contributions to ELPA seem to be
reviewed /en masse/, at an interval of about every two weeks:

http://tromey.com/elpa/news.html

It might be better for org to have a method where extension developers
can say, "There.  Fixed it." and users can get updates immediately.
People seem to do that kind of thing a lot, 'round here.  And many of
run the freshest code out there for extensions and main packages
alike.

>
> 4) adopt OLGA (Org Lisp Gadget Archive) on orgmode.org: we would
>   need to adapt package.el for a custom ELPA-like on orgmode.org
>   but this is feasible.  The advantage of having OLGA separately
>   from ELPA is that we might be more liberal about what extension
>   is allowed there.

This might work.  I like the idea of distributed repositories for ELPA
anyway, and such a move might prompt the addition of an explicit way
to include multiple package repos (debian-like) if such a way does not
exist.  I believe in a well-designed, well-used package manager for
Emacs, and whatever aids that seems to me to be a Good Thing.

> Of course, we can combine (2) and (4): have a git repos containing
> Org extensions (those who are not officially part of Emacs/Org) and
> this repo can feed our OLGA, so that users can *also* navigate and
> update Org extensions thru OLGA.

Yep.  This might be nice both for the git-crowd and those who are
inclined towards a package manager.

      reply	other threads:[~2010-09-21 23:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-10  3:21 [WISH] ELPA repo for org-mode? Jambunathan K
2010-09-21 22:38 ` Bastien
2010-09-21 23:07   ` Scot Becker [this message]

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

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to='AANLkTikVoHhEoNLRYtQMp4ux9Gb0U7eEQ-C=4mL46+zL@mail.gmail.com' \
    --to=scot.becker@gmail.com \
    --cc=bastien.guerry@wikimedia.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=kjambunathan@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).