PSC Agenda: Difference between revisions

From GRASS-Wiki
Jump to navigation Jump to search
(updated)
Line 6: Line 6:
** Prepare new promo material
** Prepare new promo material
* 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.
* 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.
* Find one or more persons to take care of [[Case Studies]].
* Find one or more persons to take care of [[Case studies]].
* Moritz Lennert suggests: have some reflection on release strategy and notably grass7 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 grass7 release. Maybe we could at least envisage some form of technology preview release that would allow us to where we stand.
* Make use of flattr.com?
* Make use of flattr.com?

Revision as of 17:53, 9 December 2012

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

Open 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
  • 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.
  • Find one or more persons to take care of Case studies.
  • Moritz Lennert suggests: have some reflection on release strategy and notably grass7 release. Maybe we could at least envisage some form of technology preview release that would allow us to where we stand.
  • Make use of flattr.com?
  • CMS: add user quotes on first page why people use GRASS?

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