wiki:PSC/Agenda

Version 16 (modified by neteler, 8 years ago) ( diff )

+Revisit PSC election procedure

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

Open issues

  • Revisit PSC renewal procedures
    • compare for example terms of the Geoserver PSC, especially regarding
      • Future PSC members
      • Stepping Down
      • Dissolution of PSC
  • Revisit PSC election procedure
    • add a candidate campaign period between nomination and elections: candidates should express what they plan to do if elected
  • PSC: assign roles to the PSC members:
    • treasurer: oversee funding model, crowdfunding and sponsoring
    • release manager
    • translation manager: find new translators, merge similar messages, ...
    • GUI design manager: implement a toolboxes based GUI
    • education and outreach manager: make it easy to teach GRASS GIS
    • press and marketing manager: develop use cases and Case studies, write short articles, CMS: add user quotes on first page why people use GRASS? Refresh start page, ...
    • documentation manager: improve manual, add more examples, ...
    • Designer: improve Website and fix mobile issues
    • trac bug report manager: cleanup tickets, followup with open questions, ...
    • Testing manager: overseeing the testing framework

Open 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)
  • discuss use of transifex for some languages

Resolved issues

2016:

2013:

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

2012 and older:

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
Note: See TracWiki for help on using the wiki.