Proposal: assign roles to the PSC members

• Please edit this Wiki page directly -

Note: a PSC member with a certain role can also delegate another community member to share the workload

Long-term working groups:

• treasurer
  • oversee funding model, crowdfunding and sponsoring
  • Financial management: set up a non-profit entity
  • Get in more ​http://grass.osgeo.org/donations/ - approach potential sponsors, develop sponsoring program
• release manager
  • get the timing right in accordance to RFC/4_ReleaseProcedure
  • follow procedure which is documented in doc/howto_release.txt
  • follow yet undocumented extra tricks (inviting package managers to create new package etc)
• translation manager
  • find new translators, cleanup similar messages in source code, ...
• education working group:
  • proactively enlarge visibility of GRASS GIS (events, press releases, articles, ...)
  • make it easy to teach GRASS GIS: collect material, advertise teaching material, ...
• academic/research working group
  • DOI, citation section in documentation
  • Errata
• press and marketing working group
  • develop use cases and ​Case studies, write short articles, CMS: add user quotes on first page why people use GRASS? Refresh start page, ...
• documentation working group
  • improve manual, add more examples, screenshots, ...
• design working group
  • prepare flyers etc.
  • improve Website and fix mobile issues
  • style and appearance of manual, gui
• trac bug report manager
  • cleanup tickets, followup with open questions, ...
• testing working group: Vaclav Petras, Soeren Gebbert
  • delegate writing tests
  • automated running of tests (continuous intergration)
  • testing framework development and maintenance
• GUI working group: Anna Petrasova, Vaclav Petras
  • general UI design
  • ensure GUI works on all platforms
  • GUI documentation, API
  • wxGUI development
  • transition to wxPython Phoenix and Python 3

Short-term working groups:

• Python 3 working group: Anna Petrasova, Vaclav Petras, Pietro Zambelli
  • provide guide to test
  • ensure 2.7 and 3 code compatibility (decide which Python 3 version is the target)
  • develop strategy for all Python components: library (scripting, pygrass, temporal), wxGUI, scripts, addons
  • track progress on separate wiki page