-
-
Notifications
You must be signed in to change notification settings - Fork 0
Tracking where are the guides are on CoPs repos and their status #2
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
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I have added another sheet to the Guides Audit to track the new issues created that are just for gathering examples |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This is a copy of the Product Management community of practice tracker with an extra column added to have the name of the CoP I am providing this as an example and option. We have not decided to use this. |
Dependency
Once we have closed all the guides that have the label "Cleaup Guide"
Overview
We need to know where the workflow for Guide contributors live for each CoP so that we can standardize the process.
Action Items
Resources/Instructions
audit spreadsheet-WIP
Organizations Google Drive: Hack for LA Guides
List of Community of Practice Guide Management Boards
Product Mangement
UI/UX
Ops - None
Admin - None
Revenue-Fundraising (No dedicated Guides Board)
Revenue-Earned Revenue - None
Engineering-Templates and Guides
Data Science-Administrative and Project Management Issues (No dedicated Guides board)
Marketing-Project Marketing (No dedicated Guides Board)
The text was updated successfully, but these errors were encountered: