-
Notifications
You must be signed in to change notification settings - Fork 89
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 CLEAN_SLATE.md #361
Add CLEAN_SLATE.md #361
Conversation
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.
love this, should be posted on HackerNews headline 👍
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.
🤘 🧹 🪨 💻
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.
!
Adding a brief style guide to for SlateDB. The The guide is meant to clarify why and how we make changes to the project. This includes: - How we decide which features should be added to SlateDB and which should be left out. - How new features should be designed and implemented. - How we evaluate changes to the project governance and decision-making processes.
No description provided.