Project Rotation: Maturity Model Labelling Workflow and Front-end

[decause-gov]

MENTOR

• @IsaacMilarky or @natalialuzuriaga
• SWE USDC 2023
• Communication Channel(s) for your team/project (e.g. Slack Channel URL, GitHub Repo URL, etc...)

BRIEF DESCRIPTION

Write a github action workflow that will:

• Run the repolinter job
• determine the the maturity model status by forking the repolinter tier4, gather booleans for specific sections (e.g.
• update the repolinter github action to output a json file with the repository report into the .github folder
• parse that file to determine what maturity model tier we suspect the repository is, and add it to the json output.
• Add a repository topic to the repository with the maturity model label

Front-end

• Use the same methodology we used for Nadia labels to add maturity model label on the metrics website.

SCOPING

• minutes
• hours
• days
• 1 week
• 2 weeks (maximum)

SKILLS NEEDED

e.g. Front-end, Back-end, Design, Product, Security, UX, Research, Webdev, Hardware, etc...

REQUIRED DELIVERABLES

Make as clear of a step-by-step list as you can

1. Draw a circle
2. Draw a triangle
3. Draw an owl

DESIRED DELIVERY WINDOW

• June
• July
• August
• Any

NOTES/INSPO

ACKNOWLEDGEMENTS

• - Yes, I agree to spend file a project proposal ticket
• - Yes, I agree this project falls within a 2 week or less (ideally less) scope of time
• - Yes, I agree to spend an hour per week of office hours and 1x1 mentoring
• - Yes, I agree to spend an hour at the end of the sprint for filling out a Retro Template

[decause-gov]

09/05:

• ACTION: @decause-gov @natalialuzuriaga Rewrite this ticket to reflect current reality