From: Jerry D <jvdelisle2@gmail.com>
To: gfortran <fortran@gcc.gnu.org>, GCC Mailing List <gcc@gcc.gnu.org>
Subject: Fwd: Hosting our gfortran MatterMost workspace
Date: Fri, 5 May 2023 10:26:35 -0700 [thread overview]
Message-ID: <5aeee11b-4844-9fe5-bfe7-5e53a9b49689@gmail.com> (raw)
In-Reply-To: <55a748dd-6b57-9e20-8ced-947d620054c3@gmail.com>
Forgot to copy the list on this.
-------- Forwarded Message --------
Subject: Re: Hosting our gfortran MatterMost workspace
Date: Fri, 5 May 2023 10:24:11 -0700
From: Jerry D <jvdelisle2@gmail.com>
To: Mark Wielaard <mark@klomp.org>
On 4/29/23 5:36 AM, Mark Wielaard wrote:
> Hi,
>
> On Fri, Apr 28, 2023 at 08:55:44PM +0200, Bernhard Reutner-Fischer wrote:
>> On 28 April 2023 18:46:07 CEST, Mark Wielaard <mark@klomp.org> wrote:
>>> OSUOSL already provides some machines for sourceware/gcc. If you
>>> could put a bit more technical details into that bugzilla issue,
>>> with expected usage (how many people, groups, moderation?) then we
>>> can coordinate and put it on the overseers agenda.
>>
>> Or you just ask Lance folks over there, but they'll need a ticket
>> anyway. As long as there is a sensible IRC adapter I'm sure nobody
>> would mind it.
>>
>> I'm not sure if anything ever happened to hosting these here, i only
>> remember a quick poll some time ago locally.
>
> Just let us know what works best for you. If you feel it could be
> useful to the rest of the gcc/sourceware community we can coordinate
> through the overseers infrastructure ticket:
> https://sourceware.org/bugzilla/show_bug.cgi?id=29853
> And we'll arrange a machine through Conservancy & OSUOSL.
>
> But if you are more comfortable setting something up just for the
> gfortran hackers and wanting to maintain it fully yourself then going
> directly to OSUOSL might be easier for you.
>
> Cheers,
>
> Mark
I have sent an email to Lance at osuosl.org and Mark to see if we can
get started on this. I am wondering how to migrate what we have now
over to a new host. I will have to query the MatterMost web pages.
Regards,
Jerry
parent reply other threads:[~2023-05-05 17:26 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <55a748dd-6b57-9e20-8ced-947d620054c3@gmail.com>]
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=5aeee11b-4844-9fe5-bfe7-5e53a9b49689@gmail.com \
--to=jvdelisle2@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.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.
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).