<!--#include virtual="/server/header.html" -->
<!-- Parent-Version: 1.92 1.98 -->
<!-- This page is derived from /server/standards/boilerplate.html -->

<title>GNU High Priority Enhancement Projects List</title>
 <!--#include virtual="/help/po/priority-projects.translist" -->
<!--#include virtual="/server/banner.html" -->
<div class="reduced-width">
<h2>GNU High Priority Enhancement Projects List</h2>
<div class="thin"></div>

<p>We are looking for programmers to add these features to various
programs (often GNU packages, but sometimes not). Please talk with the
developers of the existing program first, to discuss how best to
cooperate with them, so they will be glad to install your changes when
you have them done. Please follow all the conventions of their
project.</p>

<p>Please inform <a
href="mailto://maintainers@gnu.org"><maintainers@gnu.org></a> when you
start one of these projects, and when you have it ready to install
— or if you run into an obstacle that stops your progress.</p>


<ul>
  <li><p>Modify aspell or hunspell to handle a gender dictionary.  The
      gender dictionary for a given language would record the gender
      of each known word, if it has a gender.</p>

    <p>The purpose of this is to enhance the command to check a single word.
      It should report the word's gender, if the dictionary states its gender.
      Then we could extend the command M-$ in GNU Emacs to report the word's
      gender.  Other editors could be extended likewise.</p>
    <p>Most of us know of languages where the genders are
      “male”, “female” or perhaps
      “neuter”.  However, some languages classify nouns in
      other ways.  In linguistic terms, any classification of nouns
      into categories is called “gender”. This feature
      should let the gender dictionary specify any set of genders and
      classify nouns into them. It should handle whatever set of
      genders the current dictionary defines.</p>

    <p>Some languages use suffixes on verb forms to classify the 
      subject by gender. It would be useful if the extension can analyze a 
      verb form and say which gender it applies to its subject, 
      object, or other related nominal.</p>
  </li>

  <li><p>Write a good <em>free</em> manual for source control using Git.</p>

    <p>The git man pages are useful but, being man pages,
      they are designed to remind the user of details rather than to teach
      readers the basic concepts of using git.  This is a consequence
      of the basic structure imposed by man pages: each one is
      about one subcommand.  That is fine for reviewing the details
      of that subcommand, but the good way to organize a
      manual is by concepts.  See the <a
      href="//www.gnu.org/prep/standards/html_node/Documentation.html">
      Documentation node</a> in the GNU
      Coding Standards for more explanation.</p>
  </li>

</ul>
</div>

</div><!-- for id="content", starts in the include above -->
<!--#include virtual="/server/footer.html" -->
<div id="footer"> 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 © 2020, 2022 2023 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: 2023/07/11 09:33:39 $
<!-- timestamp end -->
</p>
</div>
</div><!-- for class="inner", starts in the banner include -->
</body>
</html>