PSC Agenda: Difference between revisions
Jump to navigation
Jump to search
(updated) |
|||
Line 7: | Line 7: | ||
''These entries need a vote from the committee members.'' | ''These entries need a vote from the committee members.'' | ||
* | * RFC3 | ||
==== Discussions ==== | ==== Discussions ==== |
Revision as of 08:39, 6 February 2008
This page contains the agenda of the GRASS Project Steering Commitee.
Open issues
Motions
These entries need a vote from the committee members.
- RFC3
Discussions
These entries do not need a formal vote.
- License issues of translation support through Rosetta - alternatively consider pootle (maybe on OSGeo infrastructure)
Resolved issues
Motions
2007
SVN write access to Eric Patton as documentation manager (granted, 24 Nov 2007)CVS write access to P. Marcondes for PT translations (granted, 2 June 2007)RFC1 Project Steering Committee guidelines- originally moved March 22, was edited and then a new motion for a vote issued April 1 (adopted April 5 2007) HTML version of SVN file
2006
CVS write access to S. Pallecchi (granted, 12 Dec 2006)PSC Chair motion (chair: M Neteler, 9 Dec 2006, see related email message)CVS write access to R. Antolin (granted, 8 Dec 2006)[1] - Legal aspects of code contributions (adopted 8 Dec 2006)
Discussions
- GRASS on koders.com: recommendation to do so. Now available here
- Add GRASS to Canonical's Rosetta translation project?
- Unresolved issue: a translation is a derivative and non-original work, and Canonical demands BSD-style copyright assignment of translations submitted through them (but not translations coming from the project). Could a translation back to english from one of those be a end-run around our copyright and the GPL?
- Update 2007: It appears that Canonical changed their Terms of use of Rosetta
See also
- List of RFCs and Motions