mainGNU Coding Standards - Summary

 
 
Show feedback again
Membership Info
Project Admin:
2 active members

Group identification
Id: #6901
System Name: gnustandards
Name: GNU Coding Standards
Group Type: Official GNU software

Search in this Group

in
   

This project is part of the GNU Project.

This project contains the Texinfo sources for the GNU Coding Standards and Information for GNU Maintainers documents. This also includes make-stds.texi, which is part of the GNU Make manual.

For the generated output in various formats, see http://www.gnu.org/prep.

Email -unavailable- with suggestions. Exact wording for proposed changes is very much appreciated. All substantive changes are approved by rms.

Registration Date: Sat 09 Oct 2004 09:13:53 PM UTC
License: GNU Free Documentation License
Development Status: 6 - Mature

 

Latest News 
undirected quoting in user messages, other recent changes
     posted by karl, Mon 02 Jan 2012 12:21:16 AM UTC - 0 replies

Some recent changes in the GNU Coding
Standards and Maintainer Information documents follow. The current versions
are available online at http://www.gnu.org/prep.

- As previously mentioned, but worth repeating, US contributors can now make use of an ...


[Read more]
contributors in US can send assignment papers electronically
     posted by karl, Wed 12 Oct 2011 11:30:58 PM UTC - 0 replies

Our friends at the Software Freedom Law Center have just informed us
that the FSF can safely accept scanned copies of signed assignments from
U.S. residents. We are also looking into the possibility of this working
for foreign contributors as well, but for now it is limited to U.S. ...


[Read more]
template text for per-package donations
     posted by karl, Sat 13 Nov 2010 12:48:11 AM UTC - 0 replies

New node with sample text for packages wishing to ask for donations: http://www.gnu.org/prep/maintain/html_node/Donations.html.

ranges can be ok in copyright lines
     posted by karl, Wed 27 Oct 2010 05:37:27 PM UTC - 0 replies

As long as information is not lost, it is now ok to use ranges in copyright years. Specifically: 1) every year in the range, inclusive, really must be a ``copyrightable'' year that would be listed individually; and 2) you make an explicit statement in a @file{README} file about this usage.

http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html has been updated.


[Submit News]
[17 news in archive]
Quick Overview

Communication Tools
Mailing Lists Mailing Lists (1 public mailing-list)

Show feedback again

Back to the top


Powered by Savane 3.1-cleanup