[FINOS_PROJECT_BLUEPRINT] - Fixes to apply
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github
- Domain
- devops
Research direction
Review the FINOS project compliance scan details and README.md, then inspect the repository collaborators and team permissions. Coordinate access changes with [email protected] or the listed maintainers, update the FINOS badge to ACTIVE, and confirm all four compliance checks are resolved.
Written by the indexing model from the issue text.
Description
NOTE! This issue was automatically generated by a FINOS GitHub Action.
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:
-
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-teams- This GitHub repository does not grant permissions to any FINOS Team, although it should be configured to grant access to the program and project specific teams defined in https://github.com/orgs/finos/teams. Please email [email protected] and coordinate changes to the repository access permissions. -
wrong-badge- Our internal records state that this project is inACTIVEstate, whereas README.md statesINCUBATING; make sure thatREADME.mdembeds the right FINOS badge. -
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.
This is a message generated by the FINOS project compliance scanning action.
For any question, do not hesitate to contact @maoo and @mcleo-d or email [email protected]. Thank you!
- Dominant language
- C
- Stars
- 0
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
docs: AGENTS.md has no rule against running deploy scripts into the owner's game installPossibly taken @thesprockee claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
EchoTools/nevr-runtime#524 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
Genymobile/scrcpy#7097 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
-
type: feature
Difficulty 1/5 Under an hour Newbie friendliness 77/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day