Initial draft of access policy

README.md

@@ -1,19 +1,29 @@
 # Data & Interoperability Working Group
 
-The Data & Interoperability Working Group aims to address challenges that the industry faces related to data management, interoperability, and integration through work that supports and enables common language, data quality, data exchange, data sharing, and data access.
+The Data & Interoperability Working Group is responsible for the oversight of initiatives related to data management, interoperability, and integration.
+
+The working group -
+  - defines and coordinates the execution of working group projects either directly or through the creation of project committees
+  - appoints representatives to work with other open source or open standards communities
+  - establishes process for release approval and security reporting
+  - defines community contribution processes (see CONTRIBUTING file)
+  - coordinates with GMG staff events and communications regarding the working group and its projects
+
+## Steering Committee
+| Name             | Position | Organisation                     | Email |
+| ---------------- | :--------: | ------------------------------ | ------------ |
+| Ben Weber | Co-chair | Amazon Web Services | bjweber@amazon.com |
+| Gustavo Pilger | Co-chair | Dassault Systèmes | | |
+
+\* marked entries denote GMG staff members, others are elected from within GMG membership.
 
 ## Projects
-| Name | Repository/Home Page |
+| Name | Project Committee Home Page |
 |--------------------|-------------------|
 | Open Mining Format | https://github.com/gmggroup/omf |
 | Common Language for Mining Technology | |
 | Interoperability Standards Landscape and Applications | |
 
-TODO
-Add detail on
-
-Meetings
-Members
-
-
 
+## Governance 
+See [GMG Governance](https://gmggroup.org/about-gmg/governance)

policy/access.md

@@ -0,0 +1,30 @@
+# GitHub Access Management Policy
+
+## Teams, not individuals
+
+Access to repositories will be granted via [GitHub teams](https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams#team-visibility) and not to individuals. 
+
+A repo may have any number of teams added to it to ensure apropriate levels of access.
+
+## Team structure
+
+Teams will be nested and aligned with the GMG Working Group hierarchy. The most deeply nested team should be the one with the highest privileges (i.e., maintain/admin).
+
+### Top level teams
+
+- [Staff](https://github.com/orgs/gmggroup/teams/staff) - GMG staff members
+- [Working Groups](https://github.com/orgs/gmggroup/teams/working-groups) - contains subteams aligned with top level Working Groups and must start with `wg-`
+- [Project Committees](https://github.com/orgs/gmggroup/teams/project-committees) - must start with `pc-
+- [Projects](https://github.com/orgs/gmggroup/teams/projects) - must start with `repo-`  
+
+## GitHub organisation membership
+
+ Membership to the [GitHub organisation](https://github.com/orgs/gmggroup/people) is not limited to paid GMG members and the wider community is welcome to join and participate. Removal from the org will only be made on advice of the GMG Executive Committee.
+
+ Note: organisation membership is required for team membership that grants specific permissions to repos
+
+## Principle of least privilege
+
+[Permissions](https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization) granted should only be as high as necessary to perform a certain role/function.
+
+- Maintain access shall be granted on a per-repo basis using the associated team and limited to current GMG members. Exceptions to the GMG membership requirement may be made by the Working Group Steering Committee in conjunction with the GMG Executive