Open choldgraf opened 1 year ago
This is great. :) Just a note on the MyST spec repo rename, if we rename the repo we should likely rename the subdomain and the NPM package (and deprecate the current package). I guess this might be coming out of my comment about naming things with clear/obvious names, if so, I think words like spec and demo are pretty clear (looks like spec is in the Oxford dictionary and the first hit on Google, for example). However, if we decide on the rename, I can help move the other things over.
I was only following the comments about fully spelling out the names - if spec
is clear enough, we can just stick with that.
That sounds great. :)
OK I've merged in the Team Compass first PR, so this now exists 🎉 https://compass.executablebooks.org
I've scoped out an issue to do some information transfer between them:
Can somebody on the @executablebooks/core-team volunteer to make the necessary changes to myst-enhancement-proposals
so that it begins to resemble the policy defined in the team-compass?
Here's a start: https://compass.executablebooks.org/en/latest/meps.html
We can then move that content out of the team compass when it's ready to go. Feel free to create new issues so that we can track this work separately like I did w/ the meta/
refactoring.
Context
We have a governance proposal described in this PR:
If merged, then the next step will be to implement those pieces. This is an issue to keep track of the steps we need to take to implement the ideas there:
To Do
team-compass/
repositorysteering-council
andcore-team
group in our github orgmyst-specification
repositorymyst-spec
tomyst-specification
myst-enhancement-proposals
repository: https://github.com/executablebooks/myst-enhancement-proposalsmyst-eps
tomyst-enhancement-proposals
After this, the Steering Council can begin iterating on formal policy for the organization.