-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
docs: formalized v1 maintenance docs #8020
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
docs: formalized v1 maintenance docs #8020
Conversation
Thanks for the PR, @JoshuaKGoldberg! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
f4369f6
to
1aabf91
Compare
This includes docs enhancements, bug fixes, and feature additions. | ||
- Non-straightforward: may be marked as approved with either two committer approvals or one maintainer approval. | ||
These include significant internal refactors and non-breaking public API changes. | ||
- "Unusual"-categorized: require a public discussion followed by two maintainer approvals. |
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.
followed by two maintainer approvals
Followup idea: maybe add committer here, for knowledge sharing? Here and for PRs.
@@ -5,14 +5,25 @@ title: Issues | |||
|
|||
This document serves as a guide for how you might manage our [GitHub Issues](https://docs.github.com/issues), also known as issue triaging. | |||
|
|||
Use your best judgement when triaging issues, and most of all remember to be **kind, friendly, and encouraging** when responding to users. | |||
Use your best judgement when triaging issues, and most of all remember to be **encouraging, friendly, and kind** when responding to users. |
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.
Nit: alphabetizing a list 😄
* docs: formalized v1 maintenance docs * Remove /team placeholder page and components * Finished TODOs * proofreading * Don't remove 'bug'
PR Checklist
Overview
Roughly copy & pastes the ratified governance proposal into our maintenance docs, significantly expanding that section of the website.