From: "pinskia at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/29853] New: mattermost instance
Date: Mon, 05 Dec 2022 18:07:51 +0000 [thread overview]
Message-ID: <bug-29853-14326@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29853
Bug ID: 29853
Summary: mattermost instance
Product: sourceware
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: Infrastructure
Assignee: overseers at sourceware dot org
Reporter: pinskia at gcc dot gnu.org
Target Milestone: ---
I have heard that having a mattermost instance would be nice. I hear the C++
GCC front-end folks are using an instance for their work. I was hearing the
gfortan folks would like to have an instance too:
https://gcc.gnu.org/pipermail/fortran/2022-December/058568.html
https://mattermost.com/
There are ways of connecting mattermost to IRC also.
https://mattermost.com/blog/connect-irc-to-mattermost/
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-12-05 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 18:07 pinskia at gcc dot gnu.org [this message]
2023-04-28 17:07 ` [Bug Infrastructure/29853] " jwakely.gcc at gmail dot com
2023-07-24 19:10 ` fche at redhat dot com
2023-08-05 17:45 ` mark at klomp dot org
2024-02-07 20:59 ` mark at klomp dot org
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=bug-29853-14326@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=overseers@sourceware.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.
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).