From: Jean Louis <bugs@gnu.support>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: emacs-devel@gnu.org, bandali@gnu.org, rms@gnu.org,
monnier@iro.umontreal.ca
Subject: Re: NonGNU ELPA
Date: Wed, 25 Nov 2020 08:52:11 +0300 [thread overview]
Message-ID: <X73xC1IFWKfZmTSL@protected.rcdrun.com> (raw)
In-Reply-To: <CADwFkmmHHjha1EqRrPW0T9r+u-GuxhPLkxh7_BOuQwQ=4u66qw@mail.gmail.com>
* Stefan Kangas <stefankangas@gmail.com> [2020-11-24 23:06]:
> I have three questions:
>
> Would it be useful to prepare a template for such a communication?
>
> Could we prepare a canonical URL for the GNU ELPA package
> requirements/rules outlined in a previous email by Richard? I assume it
> would be placed under https://elpa.nongnu.org/requirements.htm or
> something similar, once Amin can get that hostname working.
>
> Should we add a special file to nongnu.git for recording the kind of
> arrangement we decide on? I imagine that our ideal case would be number
> one above. Perhaps we would only need to note anything down when we
> have a different arrangement from the first case.
Some thoughts:
You should take notes by date on the relation with the developers as
that helps greatly other developers to understand what it is. Any
communication with developer as it is public should be quickly
accessible from such notes. If there is specific decision or anything
in the mailing list to be noted, you may insert URL to the message in
such notes.
Note could contain:
- dates of notes
- names and contact information
- sources URLs and changes of such
- references to previous decisive communication objects
next prev parent reply other threads:[~2020-11-25 5:52 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87mtzt6qhf.fsf@gnu.org>
[not found] ` <E1kbaeV-0002fw-Bm@fencepost.gnu.org>
[not found] ` <87v9eg4gm5.fsf@gnu.org>
[not found] ` <E1kbzB3-0000P3-EJ@fencepost.gnu.org>
[not found] ` <87o8k7yt7n.fsf@gnu.org>
[not found] ` <E1kciiO-0007Vp-Ms@fencepost.gnu.org>
[not found] ` <87ima56h1a.fsf@gnu.org>
2020-11-21 19:02 ` NonGNU ELPA Stefan Monnier
2020-11-21 19:10 ` Jean Louis
2020-11-21 19:30 ` Eli Zaretskii
2020-11-21 19:42 ` Amin Bandali
2020-11-21 19:41 ` Jean Louis
2020-11-21 21:14 ` Stefan Monnier
2020-11-21 21:54 ` Jean Louis
2020-11-21 23:21 ` Stefan Monnier
2020-12-04 3:52 ` Stefan Monnier
2020-12-04 7:43 ` Jean Louis
2020-12-04 13:59 ` Stefan Monnier
2020-12-05 5:21 ` Richard Stallman
2020-11-21 19:54 ` Clément Pit-Claudel
2020-11-21 21:18 ` Stefan Monnier
2020-11-21 21:57 ` Jean Louis
2020-11-21 22:21 ` Clément Pit-Claudel
2020-11-21 23:19 ` Jean Louis
2020-11-21 23:27 ` Stefan Monnier
2020-11-21 23:22 ` Stefan Kangas
2020-11-21 23:32 ` Clément Pit-Claudel
2020-11-22 0:30 ` Stefan Monnier
2020-11-22 0:40 ` Clément Pit-Claudel
2020-11-22 5:04 ` Richard Stallman
2020-11-22 15:03 ` Stefan Monnier
2020-11-23 4:44 ` Richard Stallman
2020-11-21 23:11 ` Stefan Kangas
2020-11-21 23:33 ` Stefan Kangas
2020-11-22 0:40 ` Stefan Monnier
2020-11-22 2:07 ` Stefan Kangas
2020-11-22 19:49 ` Stefan Monnier
2020-11-22 5:04 ` Richard Stallman
2020-11-24 20:05 ` Stefan Kangas
2020-11-25 5:52 ` Jean Louis [this message]
2020-11-26 4:47 ` Richard Stallman
2020-11-26 14:19 ` Stefan Monnier
2020-11-27 9:14 ` Stefan Kangas
2020-11-27 13:56 ` Stefan Monnier
2020-11-27 15:10 ` Eli Zaretskii
2020-11-27 14:59 ` Jean Louis
2020-11-27 14:56 ` Jean Louis
2020-11-27 15:21 ` Stefan Monnier
2020-11-27 16:00 ` Jean Louis
2020-11-28 8:47 ` Stefan Kangas
2020-11-27 8:54 ` Stefan Kangas
2020-11-29 5:21 ` Richard Stallman
2020-11-29 9:22 ` Stefan Kangas
2020-11-30 4:47 ` Richard Stallman
2020-11-29 5:21 ` Richard Stallman
2020-11-29 8:59 ` Andrea Corallo via Emacs development discussions.
2020-11-30 4:48 ` Richard Stallman
2020-11-22 4:58 ` Richard Stallman
2020-11-23 11:09 ` Zhu Zihao
2020-11-23 15:12 ` Stefan Monnier
2020-12-05 11:45 ` Daniel Martín
2020-12-05 13:14 ` Jean Louis
2020-12-05 13:33 ` Stefan Monnier
2020-12-05 18:37 ` Daniel Martín
2020-12-05 21:11 ` Stefan Monnier
2020-10-23 11:59 NonGNU ELPA and release frequency Antoine Kalmbach
2020-10-24 3:50 ` Richard Stallman
2020-10-24 7:08 ` Jean Louis
2020-10-24 8:41 ` Eli Zaretskii
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 14:54 ` Ivan Yonchovski
2020-10-26 4:10 ` Richard Stallman
2020-10-26 10:35 ` NonGNU ELPA Jean Louis
2020-10-27 3:47 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2020-09-11 4:21 Richard Stallman
2020-09-12 22:51 ` Tim Van den Langenbergh
2020-09-14 3:50 ` Richard Stallman
2020-09-14 8:23 ` Göktuğ Kayaalp
2020-09-15 4:38 ` Richard Stallman
2020-09-15 5:01 ` Mingde (Matthew) Zeng
2020-09-15 6:41 ` Vasilij Schneidermann
2020-09-16 5:10 ` Richard Stallman
2020-09-15 15:07 ` Thomas Fitzsimmons
2020-09-15 15:10 ` Stefan Monnier
2020-09-15 17:20 ` Thomas Fitzsimmons
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=X73xC1IFWKfZmTSL@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=bandali@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@gnu.org \
--cc=stefankangas@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.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).