From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: "Jose E. Marchesi" <jemarch@gnu.org>
Cc: Carlos O'Donell <carlos@redhat.com>, gti-tac@lists.linuxfoundation.org
Subject: Re: GTI TAC Meeting Notes 2022-11-09
Date: Wed, 9 Nov 2022 15:55:04 -0500 [thread overview]
Message-ID: <1d1817a0-f8fc-3ba1-ee7c-ce1a039285ca@gotplt.org> (raw)
In-Reply-To: <874jv7x384.fsf@gnu.org>
On 2022-11-09 15:49, Jose E. Marchesi wrote:
> I don't know what a "FSF steward" is, exactly. I have only heard the
> term in the context of GCC and glibc, and always assumed it was a
> peculiar way to refer to the GNU maintainers.
In fact I think it's specifically in the context of glibc[1], I don't
think other projects use the "FSF Stewards" or "Project Stewards" terms.
It was probably in the aftermath of the transition of the community
around 2011 where the project moved to a consensus based development
model and AFAICT the then maintainers wanted to broaden who they called
"maintainers". gcc is not the only project with a colorful history in
that regard :)
So yes, FSF Steward does refer to GNU maintainers.
> GNU maintainership is certainly well defined, both in scope and
> extension.
>
> The GNU maintainers are appointed by the GNU Project, and at the time of
> being appointed they agree to, among several other things, apply the GNU
> policies, be the responsibles for the package GNU-wide, and notify GNU
> if at some point they can't or dont want to maintain the package
> anymore.
>
> The official GNU maintainers are listed in the records in fencepost (not
> in savannah) and for the four toolchain projects they are, as of today:
<snip>
Yes, these are precisely the people who will be making decisions on
behalf of and in the interest of their respective projects.
Thanks,
Sid
[1]
https://sourceware.org/glibc/wiki/MAINTAINERS#Project_stewards_.28GNU_package_maintainers.29
next prev parent reply other threads:[~2022-11-09 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 17:47 GTI TAC Meeting Notes 2022-11-09 Carlos O'Donell
2022-11-09 18:28 ` Siddhesh Poyarekar
[not found] ` <874jv7x384.fsf@gnu.org>
2022-11-09 20:55 ` Siddhesh Poyarekar [this message]
2022-11-09 19:08 ` Jeff Law
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=1d1817a0-f8fc-3ba1-ee7c-ce1a039285ca@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=carlos@redhat.com \
--cc=gti-tac@lists.linuxfoundation.org \
--cc=jemarch@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).