You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,9 @@ Contributors must abide by the Mixed Reality Toolkit Organization's [code of con
14
14
15
15
### GitHub roles
16
16
17
-
Project roles are assigned by Maintainers via procedures outlined in the [GOVERNANCE.md](./GOVERNANCE.md) fileContributors may have one for the following roles:
17
+
Project roles are assigned by Maintainers via procedures outlined in the [Governance document](./GOVERNANCE.md).
18
+
19
+
Contributors may have one for the following roles:
18
20
19
21
***Read** Read and clone repositories. Open and comment on issues and pull requests.
20
22
***Triage** Read permissions plus manage issues and pull requests.
@@ -56,7 +58,7 @@ Maintainers have the **maintain** role, which grants write permissions plus mana
56
58
* Should have participated in multiple code reviews of other PR’s, including those of other Maintainers and Contributors.
57
59
* Should be active on the Project's community forums.
58
60
59
-
Maintainers are added and removed via procedures outlined in the [GOVERNANCE.md](./GOVERNANCE.md) file.
61
+
Maintainers are added and removed via procedures outlined in the [Governance document](./GOVERNANCE.md).
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -92,10 +92,10 @@ To help identify specific packages and their versions, MRTK3 provides an about d
92
92
93
93
This project welcomes contributions, suggestions, and feedback. All contributions, suggestions, and feedback you submitted are accepted under the [Project's license](./LICENSE.md). You represent that if you do not own copyright in the code that you have the authority to submit it under the [Project's license](./LICENSE.md). All feedback, suggestions, or contributions are not confidential.
94
94
95
-
For more information on how to contribute Mixed Reality Toolkit for Unity Project, please read [CONTRIBUTING.md](./CONTRIBUTING.md).
95
+
For more information on how to contribute Mixed Reality Toolkit for Unity Project, please read the [contributing guidelines](./CONTRIBUTING.md).
96
96
97
97
## Governance
98
98
99
-
For information on how the Mixed Reality Toolkit for Unity Project is governed, please read [GOVERNANCE.md](./GOVERNANCE.md).
99
+
For information on how the Mixed Reality Toolkit for Unity Project is governed, please read the [Governance document](./GOVERNANCE.md).
100
100
101
101
All projects under the Mixed Reality Toolkit organization are governed by the Steering Committee. The Steering Committee is responsible for all technical oversight, project approval and oversight, policy oversight, and trademark management for the Organization. To learn more about the Steering Committee, visit this link: <https://github.com/MixedRealityToolkit/MixedRealityToolkit-MVG/blob/main/org-docs/CHARTER.md>
Copy file name to clipboardExpand all lines: contributions/merging-pull-requests.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,4 +48,4 @@ A change is considered breaking if it contains incompatible API or behavior chan
48
48
49
49
### Unblocking a pull request
50
50
51
-
Only project Maintainers can unblock a pull request, and remove the "Merge: Blocked" label. To unblock a pull request, Maintainers follow the decision making rules in the [GOVERNANCE.md](../GOVERNANCE.md) file.
51
+
Only project Maintainers can unblock a pull request, and remove the "Merge: Blocked" label. To unblock a pull request, Maintainers follow the decision making rules in the [Governance document](../GOVERNANCE.md).
Copy file name to clipboardExpand all lines: contributions/opening-and-assessing-issues.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ In some cases, an issue may not be a valid discussion topic, bug, or feature req
33
33
34
34
### Project appeals
35
35
36
-
Project appeals are discussed in section 2.2 of the [GOVERNANCE.md](../GOVERNANCE.md) file. These issues can only be triaged by the Project Maintainers, and should be labeled with "Type: Appeal".
36
+
Project appeals are discussed in section 2.2 of the [Governance document](../GOVERNANCE.md). These issues can only be triaged by the Project Maintainers, and should be labeled with "Type: Appeal".
37
37
38
38
## Continue assessment
39
39
@@ -107,7 +107,7 @@ If a particular organization must resolve the issue and it’s unclear what Cont
107
107
108
108
GitHub [milestones](https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/about-milestones) should be used sparingly. Only assign a milestone if the milestone has a clear dependency on the issue.
109
109
110
-
Before a new milestone can be created in the repository, the new milestone must be approved by the project Maintainers, following the decision making rules in the [GOVERNANCE.md](../GOVERNANCE.md) file.
110
+
Before a new milestone can be created in the repository, the new milestone must be approved by the project Maintainers, following the decision making rules in the [Governance document](../GOVERNANCE.md).
Copy file name to clipboardExpand all lines: contributions/project-tenets.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,9 +24,9 @@ MRTK3 is designed to be used by developers of new and existing Unity projects. F
24
24
25
25
## Centralized project authority
26
26
27
-
MRTK3 is governed by a [steering committee](https://github.com/MixedRealityToolkit/MixedRealityToolkit-MVG/blob/main/org-docs/CHARTER.md). This committee is comprised of members from multiple companies with a vested interest in the success of MRTK. Decisions are made per the documented [governance](../GOVERNANCE.md).
27
+
MRTK3 is governed by a [steering committee](https://github.com/MixedRealityToolkit/MixedRealityToolkit-MVG/blob/main/org-docs/CHARTER.md). This committee is comprised of members from multiple companies with a vested interest in the success of MRTK. Decisions are made per the [Governance document](../GOVERNANCE.md).
28
28
29
-
Being an open source project does not mean that everyone has the ability to approve or reject changes. The [maintainers group](../MAINTAINERS.md) has the responsibility for determining if a change is appropriate and meets the project guidelines and standards. This is not to imply that the MRTK3 project does not wish to receive code review feedback from non-maintainers, we openly encourage feedback and will take it under advisement when making approval decisions.
29
+
Being an open source project does not mean that everyone has the ability to approve or reject changes. The [maintainers group](../MAINTAINERS.md) has the responsibility for determining if a change is appropriate and meets the project guidelines and standards. This is not to imply that the MRTK3 project does not wish to receive code review feedback from non-maintainers, we openly encourage feedback and will take it under advisement when making approval decisions.
0 commit comments