Next: Octave Sources (m-files), Previous: How to Contribute, Up: Contributing Guidelines

### D.2 General Guidelines

All Octave's sources are distributed under the General Public License (GPL). Currently, Octave uses GPL version 3. For details about this license, see http://www.gnu.org/licenses/gpl.html. Therefore, whenever you create a new source file, it should have the following comment header (use appropriate year, name and comment marks):

         ## Copyright (C) 1996, 1997, 2007 John W. Eaton <jwe@octave.org>
         ##
         ## This file is part of Octave.
         ##
         ## Octave is free software; you can redistribute it and/or
         ## modify it under the terms of the GNU General Public
         ## License as published by the Free Software Foundation;
         ## either version 3 of the License, or (at your option) any
         ## later version.
         ##
         ## Octave is distributed in the hope that it will be useful,
         ## but WITHOUT ANY WARRANTY; without even the implied
         ## warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
         ## PURPOSE.  See the GNU General Public License for more
         ## details.
         ##
         ## You should have received a copy of the GNU General Public
         ## License along with Octave; see the file COPYING.  If not,
         ## see <http://www.gnu.org/licenses/>.

Always include ChangeLog entries in changesets. After making your source changes, record and briefly describe the changes in the nearest ChangeLog file upwards in the directory tree. Use the previous entries as a template. Your entry should contain your name and email, and the path to the modified source file relative to the parent directory of the ChangeLog file. If there are more functions in the file, you should also include the name of the modified function (in parentheses after file path). Example:

         2010-04-13  David Bateman  <dbateman@free.fr>

         	* DLD-FUNCTIONS/regexp.cc (octregexp_list): Handle repeated matches
         	in the list of matches returned by pcre.

The ChangeLog entries should describe what is changed, not why. Any explanation of why a change is needed should appear as comments in the code, particularly if there is something that might not be obvious to someone reading it later.

The preferred comment mark for places that may need further attention is FIXME.