/*!
\page rfc2_psc RFC 2: Legal aspects of code contributions
Author: Markus Neteler (based on GDAL.org/RFC3)
Contact: neteler AT itc.it
Status: Adopted
\section legal Legal aspects
GRASS developers have to keep the code base clear of improperly
contributed code. It is important to the GRASS users, developers and
the OSGeo foundation to avoid contributing any code to the project
without it being clearly licensed under the project license or a
compliant license. In this document, a "committer" is understood to be
a developer with write access to the GRASS source code repository.
Generally speaking, the key issues are that those individuals
providing code to be included in the GRASS repository understand that
the code will be released under the GPL >=2 license, and that the
person providing the code has the right to contribute the code. In
order to verify this, the committer must have a clear understanding of
the license themselves. When committing 3rd party contributions, the
committer should verify the understanding unless the committer is very
comfortable that the contributor understands the license (for instance
frequent contributors).
If the contribution was developed on behalf of an employer (on work
time, as part of a work project, etc) then it is important that an
appropriate representative of the employer understand that the code
will be contributed under the GPL license. The arrangement should be
cleared with an authorized supervisor/manager, etc.
The code should be developed by the contributor, or the code should be
from a source which can be rightfully contributed such as from the
public domain, or from an open source project under a compatible
license.
All unusual situations need to be discussed and/or documented.
Committers should adhere to the following guidelines, and may be
personally legally liable for improperly contributing code to the
source repository:
GRASS Development Team ITC-Irst c/o M. Neteler SSI/MPA Via Sommarive, 18 38050 Trento (Povo), Italy neteler * osgeo.org*/