Finalise governance docs

[RayStick]

In the charter, there are a few places that have been highlights as 'tasks for first SC'. The first SC should resolve these queries, and update the charter.

CHARTER.md

• Write definition of what 'actively involved in a project' means

  physiopy-governance/org-docs/CHARTER.md

  Line 40 in 874311c

  - Be actively involved in a project

• Do we want to create embargo rules? To be considered with values of inclusivity, non-hierarchical governance, longevity - how to encourage turnover?

  physiopy-governance/org-docs/CHARTER.md

  Line 51 in 874311c

  **3.4 Term.** Each seat has a suggested term length of 1-3 years. Nomination to and ratification of Steering Committee membership shall proceed following the decision-making processes detailed in 3.5 & 3.6.

• Get community’s view on the choice of this license. Provide a clear rationale on any choice - a single license has been chosen to avoid conflicts of licenses across the organisation, but could be seen as too specific for some contributors

  physiopy-governance/org-docs/CHARTER.md

  Line 115 in 026d768

  - For code, an Apache 2.0 (or later) licence. If this license does not seem fit for purpose for a specific project, maintainers can request a change with the Steering Committee.

• Populate this section, noting that we already have some norms documents on the website/contributor’s guide, including all-contributors, alphabetical ordering etc.

  physiopy-governance/org-docs/CHARTER.md

  Line 122 in 026d768

  ## 10. Contribution Recognition and Authorship

TRADEMARKS.md

• Modify to reflect both software and documentation projects
• Check

  physiopy-governance/org-docs/TRADEMARKS.md

  Line 44 in aaf5840

  These guidelines are based on the [Model Trademark Guidelines](http://www.modeltrademarkguidelines.org), used under a [Creative Commons Attribution 3.0 Unported license](https://creativecommons.org/licenses/by/3.0/deed.en_US)

[m-miedema]

CODE-OF-CONDUCT.md

• This doesn't currently exist in the repo but needs to be added, likely based on but update from our website Code of Conduct (here) - which should then be linked to the governance repo, I think. In general maybe there's a nicer way to link the governance files in this repo to our website to figure out!

[RayStick]

We need to check all the documents to see if there are general points from the template (e.g. the README and project-docs folder) and make them more specific to physiopy. Refer to the google doc for our latest notes on this - mov to GH soon.

[m-miedema]

Let's indeed plan to re-tool the overall README for this directory (right now it's the default MVG one) - doesn't need to be fancy, just adapted to our use :)

[m-miedema]

to do: have AB and SC members add their names to the appropriate files!

We could consider restricting edit access to these teams as well.