/contact/gnu-advisory.html-diff
<!--#include virtual="/server/html5-header.html" -->
<!-- Parent-Version: 1.96 -->
<title>GNU Advisory Committee
- GNU Project - Free Software Foundation</title>
<!--#include virtual="/contact/po/gnu-advisory.translist" -->
<!--#include virtual="/server/banner.html" -->
<div class="reduced-width">
<h2>GNU Advisory Committee</h2>
<div class="thin"></div>
<h3>Overview</h3>
<p>The GNU Advisory Committee exists to facilitate coordination within
the GNU project. RMS (Richard Stallman), the founder of GNU and the
FSF, remains the Chief GNUisance with overall responsibility for and
authority over the GNU Project.</p>
<p>The committee's responsibilities deal with the project as a whole. It
provides an initial point of contact for questions from maintainers,
FSF and others. Members of the committee are appointed by RMS and
meet by phone each month to discuss current issues.</p>
<p>The committee can be contacted directly at
<a href="mailto:gnu-advisory@gnu.org"><gnu-advisory@gnu.org></a>.</p>
<h3>Current committee members</h3>
<ul>
<li>Alexandre Oliva</li>
(追記) <li>Amin Bandali</li> (追記ここまで)
<li>Christian Grothoff</li>
<li>Jason Self</li>
<li>Jim Meyering</li>
<li>Jose Marchesi</li>
<li>Mike Gerwitz</li>
<li>Simon Josefsson</li>
</ul>
<h3>Responsibilities</h3>
<p>The main responsibilities of the committee are to:</p>
<ul>
<li>monitor the health of the project, identifying problems and
possible solutions on behalf of RMS.</li>
<li>improve communication within the project, by taking an active
role in talking to maintainers, FSF and others.</li>
<li>be an initial contact point for issues concerning the whole
project, both internally and externally.</li>
<li>work with the FSF on maintaining the High Priority Projects list.</li>
<li>review GNU-related activities regularly, to avoid duplicate
efforts and promote existing ones, and to discuss the adoption of
prospective GNU packages.</li>
<li>be available to RMS to discuss the content of public
announcements as needed.</li>
</ul>
<h3>For GNU maintainers</h3>
<p>More information about the Advisory Committee, intended for GNU
software maintainers, is in the <a
href="/prep/maintain/maintain.html#Getting-Help">Getting
Help</a> section of the GNU Maintainers' Information document.</p>
<h3>History </h3>
<p>The committee held its first meeting in December 2009.</p>
<p>Brian Gough was a member until January 2012.</p>
<p>John Sullivan was a member until April 2021.</p>
</div>
</div><!-- for id="content", starts in the include above -->
<!--#include virtual="/server/footer.html" -->
<div id="footer" role="contentinfo">
<div class="unprintable">
<p>Please send general FSF & GNU inquiries to
<a href="mailto:gnu@gnu.org"><gnu@gnu.org></a>.
There are also <a href="/contact/">other ways to contact</a>
the FSF. Broken links and other corrections or suggestions can be sent
to <a href="mailto:webmasters@gnu.org"><webmasters@gnu.org></a>.</p>
<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
replace it with the translation of these two:
We work hard and do our best to provide accurate, good quality
translations. However, we are not exempt from imperfection.
Please send your comments and general suggestions in this regard
to <a href="mailto:web-translators@gnu.org">
<web-translators@gnu.org></a>.</p>
<p>For information on coordinating and contributing translations of
our web pages, see <a
href="/server/standards/README.translations.html">Translations
README</a>. -->
Please see the <a
href="/server/standards/README.translations.html">Translations
README</a> for information on coordinating and contributing translations
of this article.</p>
</div>
<!-- Regarding copyright, in general, standalone pages (as opposed to
files generated as part of manuals) on the GNU web server should
be under CC BY-ND 4.0. Please do NOT change or remove this
without talking with the webmasters or licensing team first.
Please make sure the copyright date is consistent with the
document. For web pages, it is ok to list just the latest year the
document was modified, or published.
If you wish to list earlier years, that is ok too.
Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
years, as long as each year in the range is in fact a copyrightable
year, i.e., a year in which the document was published (including
being publicly visible on the web or in a revision control system).
There is more detail about copyright years in the GNU Maintainers
Information document, www.gnu.org/prep/maintain. -->
<p>Copyright © 2014, 2015, 2019, 2020, (削除) 2021 (削除ここまで) (追記) 2021, 2022 (追記ここまで) Free Software Foundation, Inc.</p>
<p>This page is licensed under a <a rel="license"
href="http://creativecommons.org/licenses/by-nd/4.0/">Creative
Commons Attribution-NoDerivatives 4.0 International License</a>.</p>
<!--#include virtual="/server/bottom-notes.html" -->
<p class="unprintable">Updated:
<!-- timestamp start -->
$Date: 2025年12月29日 04:29:17 $
<!-- timestamp end -->
</p>
</div>
</div>
</body>
</html>