| | 1 | ''This page contains the agenda of the [wiki:PSC GRASS Project Steering Commitee].'' |
| | 2 | |
| | 3 | == Open issues == |
| | 4 | |
| | 5 | * PSC: assign roles to the members |
| | 6 | * Financial management: set up a non-profit entity |
| | 7 | * Get in more http://grass.osgeo.org/donations/ - approach potential sponsors, develop sponsoring program |
| | 8 | * Make use of flattr.com or other '''crowdfunding''' options (some [http://mail-pilot.com/blog/comparing-crowd-sourced-funding-platforms/ comparison]) |
| | 9 | * Find one or more persons to take care of [[Case studies]]. |
| | 10 | * CMS: add user quotes on first page why people use GRASS? Refresh start page |
| | 11 | |
| | 12 | == Motions == |
| | 13 | |
| | 14 | ''These entries need a vote from the committee members.'' |
| | 15 | |
| | 16 | * [wiki:RFC/3_PSCVotingProcedures RFC 3] (rewrite needed) |
| | 17 | |
| | 18 | == Discussions == |
| | 19 | |
| | 20 | ''These entries do not need a formal vote.'' |
| | 21 | |
| | 22 | * License issues of translation support through [https://launchpad.net/products/grass6 Rosetta] - alternatively consider [http://pootle.wordforge.org/ pootle] (maybe on OSGeo infrastructure) |
| | 23 | * discuss use of transifex for some languages |
| | 24 | |
| | 25 | == Resolved issues == |
| | 26 | |
| | 27 | * GRASS GIS - '''30th birthday upcoming'''! MN is in contact with Jim Westervelt to identify the "precise" date. So we want to celebrate that all over the globe :) And on other planets, too, since we support extraterrestrial coordinate systems. |
| | 28 | * Prepare new promo material. Best would be to get designer(s) for it. |
| | 29 | * Better populate the [http://www.youtube.com/results?search_query=grass+gis GRASS GIS videos on YouTube] - make it a channel? |
| | 30 | * Revisit the '''license of the Web pages''' and manual pages. It may be appropriate to change to a Creative Commons license which are widely accepted now. |
| | 31 | * Moritz Lennert suggests: have some reflection on release strategy and notably '''GRASS 7 release'''. Maybe we could at least envisage some form of technology preview release that would allow us to where we stand. |
| | 32 | * [wiki:PSC/Election2012 Election 2012]] |
| | 33 | * [wiki:RFC/1_ProjectSteeringCommitteeGuidelines RFC1: Project Steering Committee Guidelines] |
| | 34 | * [wiki:RFC/2_LegalAspectsOfCodeContributions RFC2: Legal aspects of code contributions] |
| | 35 | |
| | 36 | === Motions === |
| | 37 | |
| | 38 | * [wiki:PSC/Motions PSC Motions] |
| | 39 | |
| | 40 | === Discussions === |
| | 41 | |
| | 42 | <strike> |
| | 43 | * GRASS on koders.com: recommendation to do so. Now available [http://www.koders.com/info.aspx?c=ProjectInfo&pid=43B43LPYNXCC4K8PGELQYTZR5A here] |
| | 44 | </strike> |
| | 45 | |
| | 46 | * Add GRASS to Canonical's Rosetta translation project? |
| | 47 | 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? |
| | 48 | Update 2007: It appears that Canonical changed their [https://launchpad.net/legal Terms of use] of Rosetta |
