From: Eli Zaretskii <eliz@gnu.org>
To: Jean Louis <bugs@gnu.support>
Cc: rms@gnu.org, ane@iki.fi, emacs-devel@gnu.org
Subject: Re: NonGNU ELPA and release frequency
Date: Sat, 24 Oct 2020 11:41:47 +0300 [thread overview]
Message-ID: <83sga4ggms.fsf@gnu.org> (raw)
In-Reply-To: <X5PS1BRhzVZs7IER@protected.rcdrun.com> (message from Jean Louis on Sat, 24 Oct 2020 10:08:04 +0300)
> Date: Sat, 24 Oct 2020 10:08:04 +0300
> From: Jean Louis <bugs@gnu.support>
> Cc: Antoine Kalmbach <ane@iki.fi>, emacs-devel@gnu.org
>
> My proposals for plan of action for ELPA on nongnu.org are following,
> and they are not in any order:
Would you like to volunteer to do some or all of this?
Some of what you mention was already done, look in the past
discussions here. Examples:
> - [ ] establish goals purposes for non-GNU ELPA.
Done.
> - [ ] discuss the set of policies or principles for non-GNU ELPA.
Done.
> For example do we really want to see Python packages wrapped
> inside of the GNU Emacs package? I don't.
That's not policy, those are very low-level details. (And I don't see
why Python should not be allowed.)
> - [ ] decide on sub domain or URL, it could for example
> https://elpa.nongnu.org
Already done.
> - [ ] replicate GNU ELPA website in similar fashon on ELPA on
> nongnu.org without changing much, keep informing public on the
> website of the project's progress
Already decided.
next prev parent reply other threads:[~2020-10-24 8:41 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 11:59 NonGNU ELPA and release frequency Antoine Kalmbach
2020-10-23 12:24 ` Stefan Kangas
2020-10-23 18:25 ` Antoine Kalmbach
2020-10-24 3:45 ` Richard Stallman
2020-10-24 13:51 ` Antoine Kalmbach
2020-10-26 9:56 ` Philip K.
2020-10-27 3:41 ` Richard Stallman
2020-10-24 3:50 ` Richard Stallman
2020-10-24 7:08 ` Jean Louis
2020-10-24 8:41 ` Eli Zaretskii [this message]
2020-10-24 12:06 ` Jean Louis
2020-10-24 12:54 ` Eli Zaretskii
2020-10-24 14:12 ` Jean Louis
2020-10-24 14:16 ` Eli Zaretskii
2020-10-24 14:21 ` NonGNU ELPA Jean Louis
2020-10-24 14:50 ` Eli Zaretskii
2020-10-24 14:25 ` NonGNU ELPA and release frequency Antoine Kalmbach
2020-10-24 14:29 ` NonGNU ELPA Jean Louis
2020-10-24 14:40 ` Antoine Kalmbach
2020-10-24 16:37 ` Michael Albinus
2020-10-24 17:05 ` Stefan Kangas
2020-10-24 18:00 ` Antoine Kalmbach
2020-10-24 19:12 ` Michael Albinus
2020-10-25 11:40 ` Michael Albinus
2020-10-25 12:20 ` Antoine Kalmbach
2020-10-25 3:48 ` NonGNU ELPA and release frequency Richard Stallman
2020-10-25 10:29 ` Dmitry Gutov
2020-10-25 13:50 ` Stefan Monnier
2020-10-25 14:54 ` Ivan Yonchovski
2020-10-25 15:15 ` Antoine Kalmbach
2020-10-26 4:10 ` Richard Stallman
2020-10-26 10:35 ` NonGNU ELPA Jean Louis
2020-10-27 3:47 ` Richard Stallman
2020-10-26 17:37 ` NonGNU ELPA and release frequency Dmitry Gutov
2020-10-27 3:45 ` Richard Stallman
2020-10-25 3:48 ` Richard Stallman
2020-10-24 18:47 ` Stefan Monnier
2020-10-26 4:10 ` 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=83sga4ggms.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=ane@iki.fi \
--cc=bugs@gnu.support \
--cc=emacs-devel@gnu.org \
--cc=rms@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.