unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Amin Bandali <bandali@gnu.org>
To: Toon Claes <toon@iotcl.com>
Cc: Michael Albinus <michael.albinus@gmx.de>,
	Ted Zlatanov <tzz@lifelogs.com>, Fermin <fmfs@posteo.net>,
	Lars Ingebrigtsen <larsi@gnus.org>,
	emacs-devel@gnu.org
Subject: Re: Proposal for emacs-emba mailing list
Date: Tue, 29 Dec 2020 10:48:24 -0500	[thread overview]
Message-ID: <877dp0zk8n.fsf@gnu.org> (raw)
In-Reply-To: <87czys4pfs.fsf@iotcl.com>

Hello,

Toon Claes writes:

> Recently more people have shown their interest in using CI and build
> automation for GNU Emacs. Currently we have a thread going on about it
> with the people in Cc. But those mails are sent off-list.
>
> I'd like to have a mailing list to have a track record of these
> emails. We could do this on emacs-devel itself, but I'm not sure that's
> the right place (who am I to judge?). Another option could be to discuss
> on emacs-buildstatus, but that feels like an even worse idea.

+1 for discussing on them on-list; I want in as well. :-)

> Some time ago, when emba.gnu.org was initially set up, we decided to
> postpone creating a mailing list for it, because there were only 2
> people involved. I think we've come to the point were a mailing list
> would be beneficial.
>
> We could use emacs-emba, although it might be too focused to
> emba.gnu.org only, while the scope might be broader. Maybe a name like
> emacs-build-automation or so would be better. But I'm open to
> suggestions.

If we are to not use emacs-devel for those discussions but rather a
dedicated list, I'd second using a broader name than emacs-emba:
I've been floating around the idea of setting up a GNU-wide installation
of Sourcehut (at least parts of it, but especially its 'builds' module)
and inviting Emacs maintainers and interested maintainers of other GNU
packages to experiment with it and integrate it into their projects.
So, emba.gnu.org may not necessarily be present indefinitely into the
future, and I think a more generic name like emacs-build-discuss would
be better suited for such a list.



  parent reply	other threads:[~2020-12-29 15:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-29 15:11 Proposal for emacs-emba mailing list Toon Claes
2020-12-29 15:20 ` Michael Albinus
2021-01-18 15:35   ` Ted Zlatanov
2020-12-29 15:48 ` Amin Bandali [this message]
2020-12-30  2:48 ` Lars Ingebrigtsen
2020-12-30  4:57   ` Pankaj Jangid
2020-12-30  9:16     ` Michael Albinus
2020-12-30 10:01   ` Ted Zlatanov
2021-01-09 19:11     ` Proposal for emacs-build-automation mailing list (was: Proposal for emacs-emba mailing list) Michael Albinus
2020-12-30 10:23   ` Proposal for emacs-emba mailing list Toon Claes
2020-12-30 10:55     ` Michael Albinus

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=877dp0zk8n.fsf@gnu.org \
    --to=bandali@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=fmfs@posteo.net \
    --cc=larsi@gnus.org \
    --cc=michael.albinus@gmx.de \
    --cc=toon@iotcl.com \
    --cc=tzz@lifelogs.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).