finos/contrib-toolbox

A collection of utilities to support the FINOS contribution process

contrib-toolbox's Issues

Generalise to multiple programs

Right now the oc-deploy.sh is tightly coupled to the Symphony Program's activities (i.e. the ssf-dev and ssf-prod targets). In the not-too-distant future, it needs to be generalised to support any Program.

[FINOS_PROJECT_BLUEPRINT] - Fixes to apply

Consider using ScanCode to scan incoming contributions

Have you considered using scancode-toolkit to check for incoming contribs licenses? that's something I had discussed briefly with @copiesofcopies last year. I'd be glad to help!

Replace logo and Foundation text in badges

Currently the lifecycle badges show the Symphony Software Foundation logo, and the text "SSF". Both need to be replaced with the FINOS logo and name.

[FINOS_PROJECT_BLUEPRINT] - Fixes to apply - test

This is a message generated by the FINOS metadata-tool.

We have found some repository configurations that should be changed in order to comply with FINOS Governance and bylaws, see the details below.

List of fixes:

• no-issue-templates - This GitHub repository does not use issue templates; please check the issue template blueprints.
• no-badge - README.md file is missing the FINOS badge; check the README.md template and make sure that it embeds one of SVG FINOS badges.
• has-user - One or more user collaborators were found in this GitHub repository. FINOS Governance only allows GitHub users to be added via Teams. Please remove it, therefore it must be removed.
• no-code-conduct - CODE_OF_CONDUCT.md file is missing; check the CODE_OF_CONDUCT.md template.
• no-whitesource - WhiteSource configuration was not found; make sure that dependencies are scanned against security vulnerabilities. Read more on the WhiteSource Wiki page.
• notice-nok - NOTICE file is incomplete; check line 4 of the NOTICE template.
• has-admin - One or more admin collaborators were found in this GitHub repository.. FINOS Governance doesn't allow GitHub users to have Admin rights on repositories, therefore it must be removed.
  You can find more docs on the code validation ODP docs page
  For any question, do not hesitate to contact @finos-staff or email [email protected]. Thank you!

[FINOS_PROJECT_BLUEPRINT] - Fixes to apply

This is a message generated by the check-project-repos command in FINOS metadata-tool.

We have found some repository configurations that should be changed in order to comply with FINOS Governance and bylaws, see the details below.

List of fixes:

• no-issue-templates - This GitHub repository does not use issue templates; please check the issue template blueprints.
• no-badge - README.md file is missing the FINOS badge; check the README.md template and make sure that it embeds one of SVG FINOS badges.
• has-user - One or more user collaborators were found in this GitHub repository. FINOS Governance only allows GitHub users to be added via Teams. Please remove it, therefore it must be removed.
• no-code-conduct - CODE_OF_CONDUCT.md file is missing; check the CODE_OF_CONDUCT.md template.
• no-whitesource - WhiteSource configuration was not found; make sure that dependencies are scanned against security vulnerabilities. Read more on the WhiteSource Wiki page.
• notice-nok - NOTICE file is incomplete; check line 4 of the NOTICE template.
• has-admin - One or more admin collaborators were found in this GitHub repository.. FINOS Governance doesn't allow GitHub users to have Admin rights on repositories, therefore it must be removed.

You can find more docs on the code validation ODP docs page
For any question, do not hesitate to contact @finos-staff or email [email protected]. Thank you!

"operating" and "paused" badges don't have rounded corners

e.g. from the catalogue (where this is obvious):

Rename primary branches to follow best practices

Based on the opinions expressed by GitHub and within the Linux kernel, it is no longer appropriate to use the term "master" in any situations. As such, it can be safely recommended that FINOS remove any uses of the "master" branch and replace it with the new standard naming convention of main for primary branches on each repo.