Skip to content

Widen README to include community activities, not just governance #36

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
RayStick wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Widen README to include community activities, not just governance #36

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 18 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,20 +1,34 @@
<img src="pictures/phys2bids_logo2_1280×640.png" width="400">
# Physiopy Community Management

# Physiopy Governance
Welcome to Physiopy's Community Management repository!

NICE PICTURE HERE

Are you here to contribute to an upcoming Newsletter? INSTRUCTIONS HERE

Are you here to contribute to a discussion topic? INSTRUCTIONS HERE

Are you here to understand (or contribute to) Physiopy's governance procedures? *Read below.*

---

<img src="pictures/phys2bids_logo2_1280×640.png" width="200">

## Physiopy Governance

Physiopy's governance documents are based on GitHub's Minimum Viable Governance (MVP), which you can read more about here https://github.com/github/MVG. In brief, MVP is

> "... a repository-based approach for putting lightweight governance into free and open source projects that are run in version control systems."

It is a two-tier structure with [organizational governance](org-docs) and [project governance](project-docs), explained below.

## Organizational governance
### Organizational governance

At the organizational level, we have [steering committee members](org-docs/STEERING-COMMITTEE.md) and [advisory council members](org-docs/ADVISORY-COUNCIL.md). The roles of the steering committee and the advisory council are explained in the organization's [Charter](org-docs/CHARTER.md). This [Charter](org-docs/CHARTER.md) covers the organization mission, bodies (steering committee, advisory council, community members), decision making process, violations of governance terms, trademarks, confidentiality, project criteria, and contribution recognition/authorship. At the organizational level we also have the:
- [Code of conduct](org-docs/CODE-OF-CONDUCT.md)
- [GitHub Roles and Permissions for Physiopy](org-docs/PERMISSIONS.md)
- [Trademarks](org-docs/TRADEMARKS.md)

## Project governance
### Project governance

The folder [project-docs](project-docs) provides a template for individual project governance, subject to the policies and oversight of the larger organization. The MVG suggests to use these as templates for each Physiopy 'project' (probably a repository, but could be a collection of repositories). **This project governance implementation is a work in progress.**