To do

• Translate labels, milestones, epics into what those actually mean.
• What teams we have & what they do
• FYI that we're using Zenhub
• How to's / rules / how to maintain guide: Everything needs labeling, processes once a week.
• Open-ness. What we'll put up, and what we won't. We're Open by Default, but doesn't mean everything is.
• Repo description
• Link to backend for code etc.
• Todoist

Coming soon to a repo near you

• Contributing.md (@?)
• Onboarding / team guide (@natalia)

Project Management

Hotlinks

• Roadmap: https://github.com/OAButton/project-management/milestones
• Board: https://github.com/OAButton/project-management/milestones#boards?repos=67333835
• Pulse: https://github.com/OAButton/project-management/pulse

Description

This repo is to track the progress of projects/initiatives/tasks for the Open Access Button. Code issues can be found here: https://github.com/OAButton/backend

We're using Zenhub, an agile project management tool for github repositories. Download it if you don't already have it. *https://www.zenhub.com/

How to

Rules

• Issue care. A properly labeled issue has:
• A label for the teams involved, who the work is for, and if it's maintance vs development
• A Milestone
• An epic
• A clear description
• An assignment
• An estimation
• Maintain the repo by accurately labeling each new issue and placing it under an epic if applicable and including it in a milestone.

How to interpret this repository

• Assignments - the person / people responsible for the work
• Epics - The overarching goal/large task where issues fall under.
• Milestone - What we are planning to do/achieve within a time period (given month for this repo).
• Labels - Description for what area the issue falls under. Issues should have multiple labels when applicable.
• Collaboration - Issues that involve collaborating wither others outside the Open Access Button project/team/funders.
• Comms - Communications and advocacy related issues.
• Development - Issues that are active, new development. This label includes code development as well as other active development in other areas (e.g. website copy,
• Epic - Overarching goal/large task where issues fall under. Place new issues under an epic if they apply.
• Jisc - Issues that relate to the Jisc grant.
• Maintenance - Issues related to ongoing maintenance (not active development).
• Ops - Project operations related issues.
• Priority - Issues that are a high priority for the current or next milestone.
• Target - Our target for key metrics in that milestone.
• Tech - Issues related to the technology team.

Github vs Todoist

• Small things go on Todoist - e.g "Email Joe a file on Tuesday". These things will often have no use being seen externally.
• Big things go on Github - e.g every issue. These things will often be useful to show openly.

Teams

• Operations
• Joe (1/2)
• Natalia (1/3)
• Development
• Mark
• Megan (3/4)
• Natalia (1/3)
• Joe (1/2)
• Communications and Advocacy
• Chealsye
• Sarah
• Natalia (1/3)
• Megan (1/4)
• Extended family
• Penny
• Martin
• Jess

Our Teams Skills

Name/Skill	OAB Lore	Backend Dev	Frontend Dev	Bug fixing	Github use	Agile / PM'in	Copywriting	Proofreading	User Testing	Design	OAB Strategy Knowledge	Issue Expertise	Fundraising	Social
Joe	4	0	1	1	4	3	2	1	2	1	4	4	3
Chealsye	2	0	0	0	1	1
Sarah	2	0	0	0	1	1
Megan	1	0	0	0	1	1
Natalia	1	0	0	0	1	1
Mark	3	4	4	4	4	3
Jess	1	0	0	0	0	?
Martin	1	0	0	2	3	2
Penny	1	0	0	0	1	?

Our Teams Capacity

Official hours a month:

Individuals

• Joe: 32
• Mark: 64
• Megan: 48
• Chealsye: 32
• Natalia: 16-32

Teams

• Operations: 26.50
• Development: 126.5
• Communications and Advocacy: 54.5+

Our approach to Openness

We're working to make the day to day running of the project as open as possible, and make it easy for people to make contrbutions and critics of our work. However, we may obsure names or projects here if they're sensitive.