feat(0006): move GOVERNANCE.md to an AEP #359
Conversation
GOVERNANCE.md is better as an AEP that has more visibility in the project. Removing an article referring to the CNCF, since the long-term home of the project is still TBD. Minor update to @toumorokoshi's membership to reflect their new organization.
toumorokoshi
force-pushed
the
yft/add-6
branch
from
c45a4b3 to
d73eec2
Compare
There was a problem hiding this comment.
(This might be too pedantic)
Our editions deprecation policy states that we can't change AEPs for two years. I have the feeling that we'll have to make a governance change based on our long-term home. It might be best to formalize this as an AEP once we've found that long-term home.
True! For this specific AEP - is there a suggestion you had in mind in the interim? |
|
In the interim, what do you think about keeping this as GOVERNANCE.md and then we can move it to an AEP after we find a long-term home? |
|
discussed offline and agreed to move forward with this so that |
2 participants
GOVERNANCE.md is better as an AEP that has
more visibility in the project.
Removing an article referring to the CNCF, since
the long-term home of the project is still TBD.
Minor update to @toumorokoshi's membership to reflect their new organization.
🍱 Types of changes
What types of changes does your code introduce to AEP? Put an
xin the boxesthat apply
📋 Your checklist for this pull request
Please review the AEP Style and Guidance for
contributing to this repository.
General
references AEPs
correctly.
(usually
prettier -w .)./scripts/fix.py💝 Thank you!