PSC Agenda

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. Best would be to get designer(s) for it.
  • Better populate the GRASS GIS videos on YouTube - make it a channel?
• Money:
  • Set up a bank account for the GRASS GIS project
    • HB: Note the legal owner of the bank account may be on the hook for paying taxes, please review primer on the matter from the SFLC. <-- a link would be helpful
  • Get in more http://grass.osgeo.org/donations/ - approach potential sponsors
  • Make use of flattr.com or other crowdfunding options (comparison)
• 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 GRASS 7 release. Maybe we could at least envisage some form of technology preview release that would allow us to where we stand.
• CMS: add user quotes on first page why people use GRASS?

Motions

These entries need a vote from the committee members.

• RFC3: http://grass.osgeo.org/programming6/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)

---

Resolved issues

• PSC election 2012
• RFC1: Project Steering Committee Guidelines
• RFC2: Legal aspects of code contributions

Motions

• PSC 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