PSC Agenda: Difference between revisions
Jump to navigation
Jump to search
(cleanup; PSC: assign roles to the members) |
(cleanup) |
||
| Line 4: | Line 4: | ||
* PSC: assign roles to the members | * PSC: assign roles to the members | ||
* | * Financial management: set up a non-profit entity | ||
** Get in more http://grass.osgeo.org/donations/ - approach potential sponsors, develop sponsoring program | |||
** Make use of flattr.com or other '''crowdfunding''' options (some [http://mail-pilot.com/blog/comparing-crowd-sourced-funding-platforms/ comparison]) | |||
** Get in more http://grass.osgeo.org/donations/ - approach potential sponsors | |||
** Make use of flattr.com or other '''crowdfunding''' options ([http://mail-pilot.com/blog/comparing-crowd-sourced-funding-platforms/ comparison]) | |||
* Find one or more persons to take care of [[Case studies]]. | * Find one or more persons to take care of [[Case studies]]. | ||
* CMS: add user quotes on first page why people use GRASS? | * CMS: add user quotes on first page why people use GRASS? Refresh start page | ||
==== Motions ==== | ==== Motions ==== | ||
| Line 17: | Line 14: | ||
''These entries need a vote from the committee members.'' | ''These entries need a vote from the committee members.'' | ||
* RFC3: http://grass.osgeo.org/ | * RFC3: http://grass.osgeo.org/programming7/rfc3_psc.html (rewrite needed) | ||
==== Discussions ==== | ==== Discussions ==== | ||
| Line 24: | Line 21: | ||
* License issues of translation support through [https://launchpad.net/products/grass6 Rosetta] - alternatively consider [http://pootle.wordforge.org/ pootle] (maybe on OSGeo infrastructure) | * License issues of translation support through [https://launchpad.net/products/grass6 Rosetta] - alternatively consider [http://pootle.wordforge.org/ pootle] (maybe on OSGeo infrastructure) | ||
* discuss use of transifex for some languages | |||
--------------- | --------------- | ||
| Line 32: | Line 30: | ||
** Prepare new promo material. Best would be to get designer(s) for it. | ** Prepare new promo material. Best would be to get designer(s) for it. | ||
** Better populate the [http://www.youtube.com/results?search_query=grass+gis GRASS GIS videos on YouTube] - make it a channel? | ** Better populate the [http://www.youtube.com/results?search_query=grass+gis GRASS GIS videos on YouTube] - make it a channel? | ||
* 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. | |||
* 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. | * 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. | ||
* [[PSC election 2012]] | * [[PSC election 2012]] | ||
Revision as of 07:55, 1 April 2014
This page contains the agenda of the GRASS Project Steering Commitee.
Open issues
- PSC: assign roles to the members
- Financial management: set up a non-profit entity
- Get in more http://grass.osgeo.org/donations/ - approach potential sponsors, develop sponsoring program
- Make use of flattr.com or other crowdfunding options (some comparison)
- Find one or more persons to take care of Case studies.
- CMS: add user quotes on first page why people use GRASS? Refresh start page
Motions
These entries need a vote from the committee members.
- RFC3: http://grass.osgeo.org/programming7/rfc3_psc.html (rewrite needed)
Discussions
These entries do not need a formal vote.
- License issues of translation support through Rosetta - alternatively consider pootle (maybe on OSGeo infrastructure)
- discuss use of transifex for some languages
Resolved issues
- 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.
- Prepare new promo material. Best would be to get designer(s) for it.
- Better populate the GRASS GIS videos on YouTube - make it a channel?
- 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.
- 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.
- PSC election 2012
- RFC1: Project Steering Committee Guidelines
- RFC2: Legal aspects of code contributions
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