-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add the skeleton of a capability-based layout #71
Conversation
…to its own Markdown file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is looking good. A few (slightly opinionated) grammar things.
Co-authored-by: Jim Madge <[email protected]>
I've changed my review as I don't see any reason to block this. My take on the lazy consensus model was that 7 days with no objections is approval, but that isn't to say things can't be approved before 7 days. It might be worth giving this some more time for others to look at? |
@all-contributors please add @jemrobinson for content design ideas projectManagement |
I've put up a pull request to add @jemrobinson! 🎉 |
✅ Checklist
☑️ Maintainers' checklist
Add the capabilities-based skeleton discussed in the last WP1 meeting.
Main page
Standard specification page
🌂 Related issues
n/a
🙋 Acknowledging contributors