You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a Galasa maintainer, I want the project to have full marks on our GitHub community score, so that the project attracts more external contributors.
Background
Every GitHub repository has a Community rating that can be found at /community (the monorepo's for example can be found here). The community standards are a Description, README.md, Code of Conduct, CONTRIBUTING.md, License, Security Policy, Issue Template, Pull Request Template and 'Repository admins accept content reports' (unsure what this means).
We should tick off all community standards for all of our public repositories.
Tasks (for each repository)
Add a description (if a description exists but is vague, expand upon it)
Add a README.md (if a README.md exists but is vague, expand upon it)
Research more about Codes of Conduct and add one
Add a CONTRIBUTING.md (if the contributing guidelines are the same as for the 'galasa' repository, simply link back to that repository)
Add a LICENSE file
Set up a Security Policy
Issue Templates are set up on the projectmanagement repository as this is where we manage the project, so see if we can disable Issues on all the other repositories
Add a Pull Request template with the Why? and Changes section and also a section on what checks will be done to each PR to inform new contributors (functionality, code quality, unit tests if applicable, documentation if applicable, no security issues, clean commit history, etc)
Set Reported content in Settings of repository to 'Prior contributors and collaborators'
Story
As a Galasa maintainer, I want the project to have full marks on our GitHub community score, so that the project attracts more external contributors.
Background
Every GitHub repository has a Community rating that can be found at /community (the monorepo's for example can be found here). The community standards are a Description, README.md, Code of Conduct, CONTRIBUTING.md, License, Security Policy, Issue Template, Pull Request Template and 'Repository admins accept content reports' (unsure what this means).
We currently actively maintain these repositories: https://github.com/orgs/galasa-dev/repositories?type=all
We should tick off all community standards for all of our public repositories.
Tasks (for each repository)
Why?andChangessection and also a section on what checks will be done to each PR to inform new contributors (functionality, code quality, unit tests if applicable, documentation if applicable, no security issues, clean commit history, etc)