This repository has been archived by the owner on Aug 26, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 349
Maintainer Guidelines
Josh Moore edited this page Oct 20, 2023
·
1 revision
- The build script is responsible for any edits to the README.
- The README Protection Action should block any PR's that try to edit the README.
- The README is also protected by the
CODEOWNERS
file, and is owned by @degoogle-bot
- Any claims should be backed up by evidence.
- Opinions of others should be respected, but not considered as evidence.
These should be considered more carefully, especially in the case of for-profit projects.
GitHub should email me directly for these but feel free to ping me if I miss any.
- for mobile apps, when source code is available, ensure that the repo is reasonably up to date with currently supported OS versions and support schedules. For example, it may not be a great idea to accept an app that hasn’t received an update in 8 years.
- The Useful-Forks project can help maintainers find updated forks of projects.
- Users are welcome to submit via Issues, and maintainers should be the ones to open a PR if a user has not. Not every GitHub user is a developer comfortable with using Pull Requests.