From: "Jose E. Marchesi" <jemarch@gnu.org>
To: overseers@sourceware.org
Subject: Re: Proposing Sourceware as SFC member project
Date: Thu, 01 Sep 2022 00:19:59 +0200 [thread overview]
Message-ID: <87ler4qcmo.fsf@gnu.org> (raw)
In-Reply-To: <Yw5aTCLyYx8qqN3W@wildebeest.org> (Mark Wielaard's message of "Tue, 30 Aug 2022 20:43:24 +0200")
> If you have an interest in the long term future of the sourceware
> hosting server which this project is using, please consider checking
> out this thread on our local overseers@ mailing list. Everything is
> fine, we're just thinking ahead.
>
> https://sourceware.org/pipermail/overseers/2022q3/018802.html
>
> Chris Faylor <cgf@sourceware.org>
> Frank Eigler <fche@sourceware.org>
> Mark Wielaard <mark@klomp.org>
Do you plan to publish the application text before actually starting the
process? If so, where can it be found? Where can it be discussed, in
case people have comments/suggestions?
next parent reply other threads:[~2022-08-31 22:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Yw5aTCLyYx8qqN3W@wildebeest.org>
2022-08-31 22:19 ` Jose E. Marchesi [this message]
2022-09-01 8:28 ` Mark Wielaard
2022-09-02 18:51 ` Daniel Pono Takamori
2022-09-03 14:07 ` Karen M. Sandler
2022-09-03 16:38 ` Mark Wielaard
2022-09-18 19:42 ` Moving sourceware to the Linux Foundation? No thanks Christopher Faylor
2022-09-25 22:31 ` Mark Wielaard
2022-09-26 14:07 ` Ian Lance Taylor
2022-09-26 17:05 ` Christopher Faylor
2022-09-26 19:57 ` Frank Ch. Eigler
2022-09-27 13:03 ` Carlos O'Donell
2022-09-28 8:53 ` Ian Kelling
2022-10-02 21:15 ` Mark Wielaard
2022-09-28 8:33 ` Ian Kelling
2022-09-28 10:08 ` Frank Ch. Eigler
2022-09-26 21:53 ` Moving sourceware into the future Mark Wielaard
2022-09-27 17:12 ` Daniel Pono Takamori
2022-09-26 22:21 ` Moving sourceware to the Linux Foundation? No thanks Carlos O'Donell
[not found] <Yw5btfOsg6EJRvsM@wildebeest.org>
2022-09-05 15:51 ` Proposing Sourceware as SFC member project 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ler4qcmo.fsf@gnu.org \
--to=jemarch@gnu.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).