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

Finalize repo QA compliance #31

Open
10 tasks
BTT21000 opened this issue Mar 18, 2024 · 0 comments
Open
10 tasks

Finalize repo QA compliance #31

BTT21000 opened this issue Mar 18, 2024 · 0 comments
Assignees

Comments

@BTT21000
Copy link

As part of the TM issue https://github.com/api3dao/tasks/issues/849 for QA, some requirements need to be addressed:

Repo setup requirements as per new_repo_creation_checklist.md:

  • Write a short description for the repository in the description field
  • Link to some relevant page if applicable (e.g. api3 docs, web page, ...)
  • Add/remove relevant team members as collaborators (e.g., technical team, technical management members) within the repo (e.g. Steffi is no longer working on this project)
  • Grant write permissions to the appropriate team members.
  • Enhance README.md files if needed with essential high level information about the project and its scope.
  • Add the relevant license file LICENSE consistent with the organizational standards or project requirements.
  • Initialize a CONTRIBUTING.md file if applicable if the project is open to contributions from outside developers, providing guidelines for contributions.
  • Install Renovate in the repository, following the guidelines outlined in dependencyManagementStrategy.md.
  • Create a renovate.json configuration file in the root of the repository to manage dependencies effectively, as per our dependency management strategy.
  • If applicable, set up Renovate for automated security vulnerability scanning to detect vulnerabilities in the codebase.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants