Open edwardsarah opened 5 months ago
Project Board Card content & Where it Should Go
need to add new text to issues under peer review section https://github.com/hackforla/knowledgebase-content/issues/127
Start Here = Includes things like meeting times and zoom links, and anything the team members need to read. Cards that have links that you need to get to often.
Meeting times:
Friday
7:30am PDT
8:00pm IST
3:30pm WAT
4:30pm CET
Links
[Guides Project Readme](https://github.com/hackforla/guides/blob/main/README.md)
[Guides Team One-Sheet](https://github.com/hackforla/guides/issues/8)
[All Hack for LA Guides Shortcuts](https://drive.google.com/drive/folders/1buzmMJ5gCMvm3mpmdqDWryI6IBA8foKA)
[Organizations Google Drive: Hack for LA Guides](https://drive.google.com/drive/folders/1LAE_-KUd72u7vTBOTwU1Rz83rTCbeWB_?usp=sharing)
[Guides Team Figma](https://www.figma.com/file/Jz8KoGTBIxdx9jRxBWrEsF/Guides-Team-Figma?node-id=0%3A1)
[Communities of Practice](https://github.com/hackforla/communities-of-practice)
[All Guides Tracker Project board](https://github.com/orgs/hackforla/projects/3#card-72148101)
[Cleanup Guide Templates Issues](https://github.com/hackforla/guides/issues?q=is%3Aopen+is%3Aissue)
[Audit Spreadsheet for Tracking CoPs Guides](https://docs.google.com/spreadsheets/d/1mO3MPGPs3fD45XI1yuVeToqROS6n4rmY8ciGjVst9sc/edit#gid=0)
[Guides Team Slide Deck for Guide Creation](https://github.com/hackforla/guides/issues/44)
Icebox = issues identified that are going to get addressed, but are not being started yet because of other more pressing issues. Or issues that are not fully developed.
Issues that are going to get addressed, but have a blocker (usually another issue)
Where new issues get started and become ready for moving into the prioritized backlog
Add new team members to Google Drive, Have them add themselves to the roster, Add them to Figma
Bi-Weekly check on Guides that need leadership review
[Product Management](https://github.com/hackforla/product-management/issues?q=is%3Aopen+is%3Aissue+label%3A%22TG%3A+Leadership+Review%22)
[UI/UX](https://github.com/hackforla/UI-UX/issues?q=is%3Aopen+is%3Aissue+label%3A%22Guide%3A+Leadership+Review%22)
Follow up with this guide author
https://github.com/hackforla/knowledgebase-content/issues/84
Make issue for emojis (they need to be useable across platforms) see emojiterra.com for compatability
In Progress = tasks that are actively being worked on by an individual team member and have been assigned to them in the issue.
need to add new text to issues under peer review section
https://github.com/hackforla/knowledgebase-content/issues/127
- [x] Review the guide with UX/UI community of practice
- [ ] Make any changes indicated by comments
- [ ] Ask for new reviews until no suggestions for improvements are left
- [ ] Once done, remove the "Guide: Review Guide" label and add the "Guide: Leadership Review" label
Questions/Review = Issues that you are blocked on because you need an answer from another team member or other type of question/review.
### Check the Wiki to update it ###
### Aeding indicated on Slack that she would like to rejoin the team. https://hackforla.slack.com/archives/C028T9XU9S5/p1659704557772719 ###
### We need to define some other Onboarding and Offboarding situations ###
### We need to create an issue or a guide that explains all the labels in Hack For LA and how/when to use them ###
### We need to add Guide for making guides issue/templates, draft, and the guide for adding screenshots to the Resource Section of new guide template across all CoPs. See Product Management Guides for reference ###
Prioritized Backlog = features that are ready to work and a priority. This column should be prioritized by most important first.
Overview
We need to prepare the Project Boards for the forced migration that GitHub is doing in August, so that it is already working well for the team by then.
Action Items
[INSERT MARKDOWN HERE]
Resources/Instructions