Difference between revisions of "PSC Agenda"

From GRASS-Wiki
Jump to: navigation, search
(Discussions: more on rosetta problems)
Line 7: Line 7:
''These entries need a vote from each committee member.''
''These entries need a vote from each committee member.''
* March 21 vote: [[RFC1 Development Page | RFC1]] (working copy). Please edit and post major changes with a short explanation to the [[PSC]] mailing list so that it can incorporated with the CVS version [http://freegis.org/cgi-bin/viewcvs.cgi/grass6/rfc/RFC1_PSC.dox?rev=HEAD&content-type=text/vnd.viewcvs-markup RFC1] (Request For Comment) - ([http://mpa.itc.it/markus/grass63progman/rfc/rfc1_psc.html HTML version of CVS file], may be lagging behind due to manual update)
==== Discussions ====
==== Discussions ====

Revision as of 11:33, 6 April 2007

This page contains the agenda of the GRASS Project Steering Commitee.

Open issues


These entries need a vote from each committee member.


These entries do not need a formal vote.

  • License issues of translation support through Rosetta

Resolved issues


  • 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)
  • RFC2 - Legal aspects of code contributions (adopted 8 Dec 2006)


  • GRASS on koders.com: recommendation to do so. A friend of MN has submitted the code.

Did it ever make it?
  • Add GRASS to Canonical's Rosetta translation project?
Unresolved issue: a translation is a derivative and non-original work, and Cononical 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?

See also