PSC Agenda: Difference between revisions
Jump to navigation
Jump to search
(GRASS on koders.com) |
|||
| Line 30: | Line 30: | ||
==== Discussions ==== | ==== Discussions ==== | ||
<strike> | <strike> | ||
* GRASS on koders.com: recommendation to do so. | * GRASS on koders.com: recommendation to do so. Now available [http://www.koders.com/info.aspx?c=ProjectInfo&pid=43B43LPYNXCC4K8PGELQYTZR5A here] | ||
</strike> | </strike> | ||
* Add GRASS to Canonical's Rosetta translation project? | * Add GRASS to Canonical's Rosetta translation project? | ||
Revision as of 18:14, 7 April 2007
This page contains the agenda of the GRASS Project Steering Commitee.
Open issues
Motions
These entries need a vote from each committee member.
Discussions
These entries do not need a formal vote.
- License issues of translation support through Rosetta
Resolved issues
Motions
- RFC1Project Steering Committee guidelines- originally moved March 22, was edited and then a new motion for a vote issued April 1 (adopted April 5) HTML version of CVS file
- 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)
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 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
- List of RFCs and Motions