Roles in the community

The following are recognised roles within the community:

1. Community manager. Where required, the community manager has final say on any disputes. In theory this could extend from pull-requests to policy, but we expect that most technical issues will not require community manager intervention.
2. Release manager. This individual determines the contents, schedule and ultimately readiness of a release.
3. Maintainer. This individual has the responsibility to accept "pull requests" and to push the updated branch. This implies that the maintainer has reviewed the proposed changes, discussed any refinements with the originator of the pull request, and finally merged the code changes. The maintainer's primary responsibility to their mainline is, first and foremost, to do no harm(!).

If you feel that there should be more (or less!) roles defined, feel free to contribute to the users forum at TBD.

For the time being, the community manager and release managers will be XMOS employees, although we propose that this is changed once the community is up and running. In general, Maintainers will be the originators of a codebase.