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

Apply ICTU GitHub policy guidelines #4142

Closed
11 of 12 tasks
fniessink opened this issue Jul 5, 2022 · 0 comments · Fixed by #4160
Closed
11 of 12 tasks

Apply ICTU GitHub policy guidelines #4142

fniessink opened this issue Jul 5, 2022 · 0 comments · Fixed by #4160
Assignees
Projects

Comments

@fniessink
Copy link
Member

fniessink commented Jul 5, 2022

Follow the repository guidelines from the ICTU GitHub policy:

Mandatory guidelines

  • Repositories have a repository owner. The repository owner is a human being who works for ICTU.
  • Repositories have a README.md file describing the project.
  • The README.md mentions the repository owner and contact information for the repository owner.
  • Repositories have a LICENSE file.
  • Repositories have a CODE_OF_CONDUCT.md file
  • Repositories have CONTRIBUTING.md file in the root of the repository explaining how people are invited to contribute.
  • Repositories have a SECURITY.md file in the root of the repository explaining the security status and point of contact for the repository. See SECURITY.md for an example.
  • Repositories have Dependabot alerts turned on.
  • Repositories have Code scanning alerts turned on.

Optional guidelines

  • Repositories have a publiccode.yml file in the root of the repository, a metadata description standard for public software in order to make the software easily discoverable. See publiccode.yml for an example.
  • Repositories have a CHANGELOG.md file describing relevant changes to the repository contents. The changelog format is based on Keep a Changelog. See CHANGELOG.md for an example.
  • Repositories use Semantic Versioning to version the repository contents.
@fniessink fniessink added the Feature New, enhanced, or removed feature label Jul 5, 2022
@fniessink fniessink added this to Backlog in Backlog via automation Jul 5, 2022
@fniessink fniessink moved this from Backlog to Ready in Backlog Jul 5, 2022
@fniessink fniessink added Documentation and removed Feature New, enhanced, or removed feature labels Jul 5, 2022
@fniessink fniessink moved this from Ready to Refinement in progress in Backlog Jul 8, 2022
@fniessink fniessink moved this from Refinement in progress to Blocked by other issue or time in Backlog Jul 8, 2022
@fniessink fniessink moved this from Blocked by other issue or time to Ready in Backlog Jul 8, 2022
@fniessink fniessink self-assigned this Jul 8, 2022
@fniessink fniessink moved this from Ready to Development in progress (max 4) in Backlog Jul 8, 2022
@fniessink fniessink moved this from Development in progress (max 4) to Reviewing in progress in Backlog Jul 8, 2022
@fniessink fniessink linked a pull request Jul 8, 2022 that will close this issue
@fniessink fniessink moved this from Reviewing in progress to Merged in Backlog Jul 8, 2022
@fniessink fniessink moved this from Merged to Release candidate released in Backlog Jul 9, 2022
@fniessink fniessink moved this from Release candidate released to Released in Backlog Jul 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Backlog
Released
Development

Successfully merging a pull request may close this issue.

1 participant