Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Prep project boards for Migration #656

Open
3 tasks
ExperimentsInHonesty opened this issue Jun 18, 2024 · 32 comments
Open
3 tasks

Prep project boards for Migration #656

ExperimentsInHonesty opened this issue Jun 18, 2024 · 32 comments
Assignees
@gregpawin @ExperimentsInHonesty
Labels
complexity: small this issue will be very prescriptive, including info on what tools to use for each task feature: GitHub hygiene missing: milestone role: product manager size: 1pt Can be done in 6 hours or less

Comments

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Jun 18, 2024 •
edited
Loading

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

  • copy this template to a comment below 
    ### Text from project board card, [Add name of column here]
```
[INSERT MARKDOWN HERE]
```
- [ ] Determine where this item goes on the wiki (page and section)
- [ ] copy item to wiki
- [ ] hide this comment when completed.
  • copy markdown from a card in the "Start Here" column of the Project Board into your new comment, where it says `[INSERT MARKDOWN HERE]
  • delete card from project board.

Resources/Instructions
@ExperimentsInHonesty ExperimentsInHonesty added role: product manager complexity: small this issue will be very prescriptive, including info on what tools to use for each task size: 1pt Can be done in 6 hours or less missing: milestone feature: GitHub hygiene labels Jun 18, 2024
@ExperimentsInHonesty
Copy link
Member Author

Text from Main Project Board card, Information column

Meetings on Monday at 6pm. Check Slack channel for link.
  • Determine where this item goes on the wiki (page and section)
  • copy item to wiki
  • hide this comment when completed.

@ExperimentsInHonesty
Copy link
Member Author

Text from Main Project Board card, Information column

**Links**
* [Hack for LA Project Page](https://www.hackforla.org/projects/lucky-parking)
* [Meeting Minutes](https://github.com/hackforla/lucky-parking/issues/375)
* [Beta Site](http://www.luckyparking.org/)
* [Google Drive](https://drive.google.com/drive/folders/1dYD6aqeC-uncWkX77a38NN_sPhC9dgAe?usp=sharing)
* [Roster Sheet](https://docs.google.com/spreadsheets/d/1rtou2FkVwKV7-2RKiRDXb2uAq_w0jHakFydzUhoW2dU/edit#gid=1467771315)
* [Market Research](https://docs.google.com/document/d/1aFQcmFRtMojy3d0TK07ulfuenJG5DvPXm0y2vjKIK1g/edit?usp=sharing)
* [Project-one-sheet](https://docs.google.com/document/d/1wKe_zq1El-fWpn6kYA_9X0ej3Pic0HxLeX-e-S9Mz0Y/edit)
* [Google Calendar](https://calendar.google.com/calendar/embed?src=luckyparking%40hackforla.org&ctz=America%2FLos_Angeles)
  • Determine where this item goes on the wiki (page and section)
  • copy item to wiki
  • hide this comment when completed.

@gregpawin
Copy link
Member

gregpawin commented Jun 24, 2024 •
edited
Loading

Text from UI/UX board card, Resources

Figma File:
https://www.figma.com/files/team/1041165488905070933/Lucky-Parking's-team?fuid=849688382617586392
  • Determine where this item goes on the wiki (page and section)
  • copy item to wiki
  • hide this comment when completed.

@gregpawin
Copy link
Member

Text from UI/UX board card, Resources

GOOGLE DRIVE:
https://drive.google.com/drive/folders/1dYD6aqeC-uncWkX77a38NN_sPhC9dgAe?usp=sharing
  • Determine where this item goes on the wiki (page and section)
  • copy item to wiki
  • hide this comment when completed.

@gregpawin
Copy link
Member

Text from UI/UX board card, Resources

**COLOR CONTRAST TOOLS**
* [Adobe Color Wheel -  Color Blind Simulator](https://color.adobe.com/create/color-accessibility)
* [Accessible Color Palette Builder](https://toolness.github.io/accessible-color-matrix/?n=white&n=Color%202&n=Color%203&n=Color%204&n=Color%205&v=FFFFFF&v=FEDC2A&v=5A3B5D&v=8B538F&v=C3A3C9)
* [Accessible Contrast Grid - check WCAG 2.0 standard](https://contrast-grid.eightshapes.com/?background-colors=%23FFFFFF%2C%20White%0D%0A%23FEDC2A%2C%20Yellow%0D%0A%235A3B5D%2C%20Dark%20Purple%0D%0A%238B538F%2C%20Light%20Purple%0D%0A%23C3A3C9%2C%20Lightst%20purple%0D%0A%23777777%2C%20Gray%0D%0A%23555555%2C%20Darker%20Gray%0D%0A%0D%0A&foreground-colors=%23FFFFFF%2C%20White%0D%0A%23F2F2F2%0D%0A%23DDDDDD%0D%0A%23CCCCCC%0D%0A%23888888%0D%0A%23404040%2C%20Charcoal%0D%0A%23000000%2C%20Black%0D%0A%232F78C5%2C%20Effective%20on%20Extremes%0D%0A%230F60B6%2C%20Effective%20on%20Lights%0D%0A%23398EEA%2C%20Ineffective%0D%0A&es-color-form__tile-size=compact)
  • Determine where this item goes on the wiki (page and section)
  • copy item to wiki
  • hide this comment when completed.

@gregpawin
Copy link
Member

Text from Main Project Board card, Information

### [Card] Sorted by Role
* [Data Scientist](https://github.com/hackforla/lucky-parking/projects/3?card_filter_query=label%3A%22role%3A+data+scientist%22+-is%3Aclosed)
* [Product Manager](https://github.com/hackforla/lucky-parking/projects/3?card_filter_query=label%3A%22role%3A+product+manager%22+-is%3Aclosed)
* [UI/UX](https://github.com/hackforla/lucky-parking/projects/3?card_filter_query=label%3A%22role%3A+ui%2Fux%22+-is%3Aclosed)
* [Frontend](https://github.com/hackforla/lucky-parking/projects/3?card_filter_query=label%3A%22role%3A+frontend%22+-is%3Aclosed)
* [Backend](https://github.com/hackforla/lucky-parking/projects/3?card_filter_query=label%3A%22role%3A+backend%22+-is%3Aclosed)
* [Devops](https://github.com/hackforla/lucky-parking/projects/3?card_filter_query=label%3A%22role%3A+devops%22+-is%3Aclosed)
* [Dev](https://github.com/hackforla/lucky-parking/projects/3?card_filter_query=label%3A%22role%3A+dev%22+-is%3Aclosed)
  • Determine where this item goes on the wiki (page and section)
  • copy item to wiki
  • hide this comment when completed.

@gregpawin
Copy link
Member

Text from Main Project Board card, Information

Figma File:
https://www.figma.com/files/team/1041165488905070933/Lucky-Parking's-team?fuid=849688382617586392
  • Determine where this item goes on the wiki (page and section)
  • copy item to wiki
  • hide this comment when completed.

@ExperimentsInHonesty

This comment was marked as resolved.

Sign in to view
@ExperimentsInHonesty
Copy link
Member Author

Text from Main Project Board card, Product Backlog

Issues that have been reviewed, estimated, and prioritized top-to-bottom.
  • Determine where this item goes on the wiki (page and section)
  • copy item to wiki
  • hide this comment when completed.

@ExperimentsInHonesty
Copy link
Member Author

ExperimentsInHonesty commented Jun 24, 2024 •
edited
Loading

Text from project board card, Priority Backlog

Issues that have been selected to be completed in the sprint, prioritized top-to-bottom.
  • Determine where this item goes on the wiki (page and section)
  • copy item to wiki
  • hide this comment when completed.

@ExperimentsInHonesty
Copy link
Member Author

ExperimentsInHonesty commented Jun 24, 2024 •
edited
Loading

Text from project board card, In Progress

Issues actively being worked on by the team.
  • Determine where this item goes on the wiki (page and section)
  • copy item to wiki
  • hide this comment when completed.

@ExperimentsInHonesty
Copy link
Member Author

Text from project board card, [Add name of column here]

[INSERT MARKDOWN HERE]
  • Determine where this item goes on the wiki (page and section)
  • copy item to wiki
  • hide this comment when completed.

1 similar comment
@ExperimentsInHonesty
Copy link
Member Author

Text from project board card, [Add name of column here]

[INSERT MARKDOWN HERE]
  • Determine where this item goes on the wiki (page and section)
  • copy item to wiki
  • hide this comment when completed.

@gregpawin
Copy link
Member

Text from Main Project Board card, Release

Issues ready to be released to production following completion of code and product review.
  • Determine where this item goes on the wiki (page and section)
  • copy item to wiki
  • hide this comment when completed.

@gregpawin
Copy link
Member

Text from project board card, Product Review

Issues open for product and acceptance criteria review.
  • Determine where this item goes on the wiki (page and section)
  • copy item to wiki
  • hide this comment when completed.

@gregpawin
Copy link
Member

Text from Main Project board card, Internal Team Review

Issues open for internal team review (i.e., code review for developers, etc.).
  • Determine where this item goes on the wiki (page and section)
  • copy item to wiki
  • hide this comment when completed.

@gregpawin
Copy link
Member

Text from project development board card, Information

**Links**
* [Team Roster](https://docs.google.com/spreadsheets/d/1MKMq_0hej7a5iVG4JQA6XH_w7sDlmGjI/edit?usp=sharing&ouid=112419281916974761448&rtpof=true&sd=true)
* [Hack for LA Project Page](https://www.hackforla.org/projects/lucky-parking)
* [Meeting Minutes](https://docs.google.com/document/d/1Sjm15xIJVcOh8qZl3wgyMGqSC5PIXyjV/edit?usp=sharing&ouid=112419281916974761448&rtpof=true&sd=true)
* [Google Drive](https://drive.google.com/drive/folders/1dYD6aqeC-uncWkX77a38NN_sPhC9dgAe?usp=sharing)
* [Figma](https://www.figma.com/file/R3N7mvDtlFbFgQm4OXcMih/Lucky-Parking?node-id=0%3A1)
* [Project-one-sheet](https://docs.google.com/document/d/1wKe_zq1El-fWpn6kYA_9X0ej3Pic0HxLeX-e-S9Mz0Y/)
  • Determine where this item goes on the wiki (page and section)
  • copy item to wiki
  • hide this comment when completed.

@gregpawin
Copy link
Member

Text from project development board card, New Issues

Stories to be reviewed, estimated, and groomed before being added to the Product Backlog
  • Determine where this item goes on the wiki (page and section)
  • copy item to wiki
  • hide this comment when completed.

@gregpawin
Copy link
Member

Text from project development board card, Epics

Long-term goals, organized by grouping related stories together.
  • Determine where this item goes on the wiki (page and section)
  • copy item to wiki
  • hide this comment when completed.

@gregpawin
Copy link
Member

Text from project development board card, Product Backlog

Stories that have been reviewed, estimated, and prioritized top-to-bottom.
  • Determine where this item goes on the wiki (page and section)
  • copy item to wiki
  • hide this comment when completed.

@gregpawin
Copy link
Member

gregpawin commented Jun 24, 2024 •
edited
Loading

Text from project development board card, Sprint Backlog

Stories selected to be completed in the sprint, prioritized top-to-bottom.
  • Determine where this item goes on the wiki (page and section)
  • copy item to wiki
  • hide this comment when completed.

@gregpawin
Copy link
Member

Text from project development board card, Blocked

Stories that are blocked or on-hold from being actively worked on.
  • Determine where this item goes on the wiki (page and section)
  • copy item to wiki
  • hide this comment when completed.

@gregpawin
Copy link
Member

Text from project development board card, In Progress

Stories actively being worked on by the team.
  • Determine where this item goes on the wiki (page and section)
  • copy item to wiki
  • hide this comment when completed.

@gregpawin
Copy link
Member

Text from project development board card, In Review

Stories open for code review and acceptance testing.
  • Determine where this item goes on the wiki (page and section)
  • copy item to wiki
  • hide this comment when completed.

@gregpawin
Copy link
Member

Text from project development board card, Accepted

Stories that have passed review and are ready to be released.
  • Determine where this item goes on the wiki (page and section)
  • copy item to wiki
  • hide this comment when completed.

@gregpawin
Copy link
Member

Text from project development board card, Done

Stories that have been released to production.
  • Determine where this item goes on the wiki (page and section)
  • copy item to wiki
  • hide this comment when completed.

@ExperimentsInHonesty
Copy link
Member Author

Text from Product Management project board (closed) card, Links / Questions / In Review

Has links on it that the other links above does not.

**Links**
* [Meeting Minutes](https://drive.google.com/file/d/1g5DmbiQrfxi8F8Vaj6fHjp1X1AnP2Acl/view?usp=sharing)
* [Market Research Doc](https://docs.google.com/document/d/1aFQcmFRtMojy3d0TK07ulfuenJG5DvPXm0y2vjKIK1g/edit?usp=sharing)
* [Beta Site](http://luckyparking.info/)
* [Google Drive](https://drive.google.com/drive/u/0/folders/1qq6w-eCvjxgfiQCCxPN9_0ah1DLTgl27)
* [Roster Sheet](https://docs.google.com/spreadsheets/d/1wsHeQrQNhOdjv5zl_xCcvbXo9OEFWddDPXCyxzs2EfQ/edit?usp=sharing)
* [Project-one-sheet](https://docs.google.com/document/d/1wKe_zq1El-fWpn6kYA_9X0ej3Pic0HxLeX-e-S9Mz0Y/)
  • Determine where this item goes on the wiki (page and section)
  • copy item to wiki
  • hide this comment when completed.

@ExperimentsInHonesty
Copy link
Member Author

ExperimentsInHonesty commented Jun 24, 2024 •
edited
Loading

Text from Archived: Machine Learning & Archived: Beginning Task project boards cards, Ice Box

Ice Box = Issues identified that are going to get address, but are not being started yet because of other more pressing issues.
  • Determine where this item goes on the wiki (page and section)
  • copy item to wiki
  • hide this comment when completed.

@ExperimentsInHonesty
Copy link
Member Author

ExperimentsInHonesty commented Jun 24, 2024 •
edited
Loading

Text from Archived: Machine Learning & Archived: Beginning Task project boards cards, Prioritized Backlog

Prioritized Backlog = features that are to do and a priority.
  • Determine where this item goes on the wiki (page and section)
  • copy item to wiki
  • hide this comment when completed.

@ExperimentsInHonesty
Copy link
Member Author

ExperimentsInHonesty commented Jun 24, 2024 •
edited
Loading

Text from Archived: Machine Learning & Archived: Beginning Task project boards cards, In Progress

In Progress = tasks that are actively being worked on an individual team member and have been assigned to them in the issue.
  • Determine where this item goes on the wiki (page and section)
  • copy item to wiki
  • hide this comment when completed.

@ExperimentsInHonesty
Copy link
Member Author

ExperimentsInHonesty commented Jun 24, 2024 •
edited
Loading

Text from Archived: Machine Learning & Archived: Beginning Task project boards cards, Done

Done = Task Completed
  • Determine where this item goes on the wiki (page and section)
  • copy item to wiki
  • hide this comment when completed.

@ExperimentsInHonesty ExperimentsInHonesty moved this from New Issues to In Progress in P: LP: Project Board Jun 24, 2024
@ExperimentsInHonesty
Copy link
Member Author

ExperimentsInHonesty commented Jun 24, 2024 •
edited
Loading

@gregpawin I did the following over the last few hours

  • added labels to each of the issues to show what boards they came from
  • created board views on the LP: Project Board
  • engineering is the only board that the issues are currently on, both the project board and the engineering board. This is ready for discussion.
    • The engineering board has some additional details that are not currently setup on the project board, and need to be discussed with the HfLA org rep before changes are made.
    • I mapped each open engineering issue manually
  • I updated this issue and its links and the issues that are missing labels Weekly Label Check #382 (comment)
    • The board views will be useful when the proper labels are used (listed in order of importance)
      • role : so that the board view shows all the issues for that role
      • complexity: so that you know in which order you should do them as a person who is taking on issues from good first, through extra large
      • size: how long we think it will take you, based on who would be working on that complexity level and the amount of work to do
      • feature: tells you what you are working on and generally should correspond to a wiki page that has resources (links and documentation about both the history of that feature and any file locations, documentation, tutorials, etc.).

Next steps

  • After the role labels have been added. We can review the board views that represent the classic boards and get whatever information that we find relevant, and then delete the view.
  • Add the complexity labels to the issues that need them (see the role views, for the ones that you will most likely be able to add labels to)
    • why do we need the complexity labels: so that you know in which order you should do them as a person who is taking on issues from good first, through extra large

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gregpawin gregpawin

@ExperimentsInHonesty ExperimentsInHonesty

Labels
complexity: small this issue will be very prescriptive, including info on what tools to use for each task feature: GitHub hygiene missing: milestone role: product manager size: 1pt Can be done in 6 hours or less
Projects
P: LP: Project Board
Status: In Progress
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gregpawin @ExperimentsInHonesty