Skip to content
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

Merged

Conversation

JoshuaKGoldberg
Copy link
Member

@JoshuaKGoldberg JoshuaKGoldberg commented Dec 3, 2023

PR Checklist

Overview

Roughly copy & pastes the ratified governance proposal into our maintenance docs, significantly expanding that section of the website.

@typescript-eslint
Copy link
Contributor

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.

Copy link

netlify bot commented Dec 3, 2023

Deploy Preview for typescript-eslint ready!

Name Link
🔨 Latest commit 589d9ae
🔍 Latest deploy log https://app.netlify.com/sites/typescript-eslint/deploys/658788565c31bf0008b85663
😎 Deploy Preview https://deploy-preview-8020--typescript-eslint.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 98 (no change from production)
Accessibility: 100 (no change from production)
Best Practices: 92 (no change from production)
SEO: 98 (no change from production)
PWA: 80 (no change from production)
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify site configuration.

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.
Copy link
Member Author

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.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: alphabetizing a list 😄

@JoshuaKGoldberg JoshuaKGoldberg marked this pull request as ready for review December 12, 2023 20:21
bradzacher
bradzacher previously approved these changes Dec 23, 2023
@JoshuaKGoldberg JoshuaKGoldberg merged commit 7c79f54 into typescript-eslint:main Dec 24, 2023
56 of 57 checks passed
@JoshuaKGoldberg JoshuaKGoldberg deleted the maintenance-docs branch December 24, 2023 05:11
auvred pushed a commit to auvred/typescript-eslint that referenced this pull request Dec 29, 2023
* docs: formalized v1 maintenance docs

* Remove /team placeholder page and components

* Finished TODOs

* proofreading

* Don't remove 'bug'
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Docs: Formalize the v1 governance proposal into docs
2 participants