PSC Agenda: Difference between revisions

From GRASS-Wiki
Jump to navigation Jump to search
m (url fix)
(removed redundancy with other pages)
Line 2: Line 2:


=== Open issues ===
=== Open issues ===
* [[PSC election 2012]]


==== Motions ====
==== Motions ====
Line 18: Line 20:


=== Resolved issues ===
=== Resolved issues ===
* [http://grass.osgeo.org/programming6/rfc1_psc.html RFC1: Project Steering Committee Guidelines]
* [http://grass.osgeo.org/programming6/rfc2_psc.html RFC2: Legal aspects of code contributions]


==== Motions ====
==== Motions ====


2008
* [http://grass.osgeo.org/programming6/psc_motions.html PSC Motions]
* <strike>SVN write access to Ivan Shmakov (granted, 6 Feb 2008)</strike>
 
2007
* <strike>SVN write access to Eric Patton as documentation manager (granted, 24 Nov 2007)</strike>
* <strike>Motion to [http://www.nabble.com/Motion%3A-migrate-to-SVN-trac-on-OSGeo-infrastructure-tf4633839.html migrate] CVS/bugtracker to OSGeo (passed, 22 Oct 2007)</strike>
* <strike>CVS write access to P. Marcondes for PT translations (granted, 2 June 2007)</strike>
* <strike>[[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)  [http://download.osgeo.org/grass/grass6_progman/rfc/rfc1_psc.html HTML version of SVN file]</strike>
 
2006
* <strike>CVS write access to S. Pallecchi (granted, 12 Dec 2006)</strike>
* <strike>PSC Chair motion (chair: M Neteler, 9 Dec 2006, [http://grass.itc.it/pipermail/grass-psc/2006-December/000143.html see related email message])</strike>
* <strike>CVS write access to R. Antolin (granted, 8 Dec 2006)</strike>
* <strike>[http://download.osgeo.org/grass/grass6_progman/rfc/rfc2_psc.html] - Legal aspects of code contributions (adopted 8 Dec 2006)</strike>


==== Discussions ====
==== Discussions ====
Line 44: Line 36:
: 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?
: 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 [https://launchpad.net/legal Terms of use] of Rosetta
:: Update 2007: It appears that Canonical changed their [https://launchpad.net/legal Terms of use] of Rosetta
=== See also ===
* List of [http://download.osgeo.org/grass/grass6_progman/rfc/ RFCs and Motions]


[[Category: PSC]]
[[Category: PSC]]

Revision as of 11:04, 29 October 2012

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

Open issues

Motions

These entries need a vote from the committee members.

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

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