|
|
This page describes the Project Steering Committee of iota2.
|
|
|
This page describes the Project Steering Committee of iota2. It is inspired by [OTB](https://www.orfeo-toolbox.org/) Project Steering Committee.
|
|
|
|
|
|
## PSC scope
|
|
|
[[_TOC_]]
|
|
|
|
|
|
### Roadmaps
|
|
|
### Communication
|
|
|
### User support and documentation
|
|
|
### Contribution management
|
|
|
### Release planning
|
|
|
### Handling of legal issues |
|
|
# PSC scope
|
|
|
The aim of the iota2 Project Steering committee (PSC) is to provide high level guidance and coordination for the iota2 project.
|
|
|
|
|
|
It provides a central point of contact for the project and arbitrates disputes. It is also a stable base of "institutional knowledge" to the project and tries its best to involve more developers and users.
|
|
|
|
|
|
It should help to guarantee that iota2 remains open and company neutral.
|
|
|
|
|
|
## Roadmaps
|
|
|
The PSC gathers and publishes high level roadmaps for iota2:
|
|
|
* Feature roadmap,
|
|
|
* Technical roadmap (developer and coding guidelines and workflows, target systems, packaging ...),
|
|
|
* Infrastructure roadmap (SCM, wiki, dashboard ...).
|
|
|
|
|
|
The PSC also publishes the guidelines and the acceptance policy for feature requests. It enforces them. It monitors and approves new feature requests.
|
|
|
|
|
|
## Communication
|
|
|
The PSC coordinates communication actions:
|
|
|
* Ensures that the wiki is up-to-date,
|
|
|
* Ensures that the website is up-to-date and proposes new content,
|
|
|
* Ensures regular posting on the blog and social networks,
|
|
|
* Keeps track of opportunities to communicate: Symposium and events where iota2 could be represented,
|
|
|
* Keeps track of opportunities from communities: Google Summer of Code project, link with other OSGeo and FOSS projects,
|
|
|
* Is responsible for the organization of events around iota2 (i.e. users meetings and hackathon).
|
|
|
|
|
|
## User support and documentation
|
|
|
The PSC ensures that users are given an appropriate support:
|
|
|
* Ensures that support is working (unanswered questions, questions from other places than the user list ...)
|
|
|
* Proposes addition to the documentation based on users feedback,
|
|
|
* Proposes new features for the roadmap based on users feedback,
|
|
|
* Proposes new ways for support and documentation.
|
|
|
|
|
|
## Contribution management
|
|
|
The PSC publishes the guidelines and acceptance policy for contributions. It enforces them.
|
|
|
|
|
|
It monitors and approves new proposals.
|
|
|
|
|
|
It ensures that contribution is as easy as possible, by monitoring technical means for contribution and proposing evolution to guidelines, policies and means.
|
|
|
|
|
|
## Release planning
|
|
|
The PSC publishes release guidelines and policies, and enforces them.
|
|
|
|
|
|
The PSC puts together the next Release roadmap and proposes a planning. It is then responsible for the release preparation.
|
|
|
|
|
|
The final approval for a release is given by the PSC.
|
|
|
|
|
|
## Handling of legal issues
|
|
|
The PSC is responsible for addressing any issue about copyright or licensing that may occur, and most importantly, it is responsible for taking preventive actions about those issues.
|
|
|
|
|
|
# How does the PSC work?
|
|
|
This section describes how the PSC works.
|
|
|
|
|
|
## |
|
|
\ No newline at end of file |