Skip to content

Commit d41b267

Browse files
authored
Add xref to compass and core team
1 parent 21a5925 commit d41b267

File tree

3 files changed

+4
-4
lines changed

3 files changed

+4
-4
lines changed

index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ A formal process for changing [the MyST Markdown Specification](https://mystmd.o
77
Because the MyST specification has many interior and exterior stakeholders, we use a more formal and structured process around changing the specification[^gov].
88
These are called **MyST Enhancement Proposals (MEPs)**.
99

10-
[^gov]: See [our Team Compass](https://compass.jupyterbook.org) for other governance and decision-making processes in the Executable Books community.
10+
[^gov]: See [our Team Compass](xref:compass) for other governance and decision-making processes in the Executable Books community.
1111

1212
This process is encoded in https://github.com/jupyter-book/myst-enhancement-proposals and in this documentation.
1313
The sections below describe the process, and the [](list.md) is where you can find all of our MEPs.

myst.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ project:
2929
open_access: true
3030
license: CC-BY-4.0
3131
references:
32-
compass: https://compass.executablebooks.org/en/latest/
32+
compass: https://compass.jupyterbook.org/
3333
plugins:
3434
- mep.mjs
3535
site:

overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -68,10 +68,10 @@ Once the proposal has stabilized and the author wishes to move forward, do the f
6868
- To request blocking changes, then click `Request Changes` in the GitHub UI. (see [](#appendix:blocking))
6969
- A MEP may be accepted when all of the following conditions are met:
7070
- More than five (5) weekdays have passed since the proposal was marked as `Active`.
71-
- At least two `PR Approvals` from **core team members**.
71+
- At least two `PR Approvals` from [**core team or steering council members**](xref:compass#team).
7272
- No `Request Changes` from a core team member.
7373
- If there are **unresolved objections** (via `Request Changes` to the PR)
74-
- The MEP author may restart the voting process after incorporating feedback to resolve the objection, **or** ask the Steering Council to follow the same [decision-making process used for team policy](xref:compass#governance:policy-decision).
74+
- The MEP author may restart the voting process after incorporating feedback to resolve the objection, **or** ask the Steering Council to follow the same [decision-making process used for team policy](xref:compass#governance).
7575
- If there are no unresolved objections, the MEP is **accepted**:
7676
- Update its status metadata to `Accepted` and merge the PR.
7777
- Once a PR is merged, it closes the issue and a decision has been made.

0 commit comments

Comments
 (0)