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.

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

Lead Dashboard: Dev #4294

Open
3 tasks
ExperimentsInHonesty opened this issue Mar 26, 2023 · 18 comments
Open
3 tasks

Lead Dashboard: Dev #4294

ExperimentsInHonesty opened this issue Mar 26, 2023 · 18 comments
Labels
Complexity: Medium Dependency An issue is blocking the completion or starting of another issue Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly frequency: weekly tasks that have to be done every week. Issue never closes role: dev leads Tasks for technical leads role: product Product Management size: 1pt Can be done in 4-6 hours

Comments

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Mar 26, 2023

Dependency

Overview

We need to create a dashboard so that it is easy for Dev Leads to know where to focus their effort to maintain a healthy backlog of issues for each complexity type while addressing time sensitive requirements.

Action Items

  • Create a dashboard below in a comment by using template
  • Iterate
  • Once stable, discuss with Leads best way to make it automatic

Template

# Full report
Dev Dashboard 
Date:

Good First Issue front end & back end
[Prioritized Backlog](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22good+first+issue%22+label%3A%22role%3A+front+end%22+label%3A%22role%3A+back+end%2Fdevops%22#column-7198257) :  
[New Issue Approval](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22good+first+issue%22+label%3A%22role%3A+front+end%22+label%3A%22role%3A+back+end%2Fdevops%22#column-15235217): 
[ERs](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22good+first+issue%22+label%3A%22role%3A+front+end%22+label%3A%22role%3A+back+end%2Fdevops%22#column-19403960): 

Small backend
[Prioritized Backlog](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22complexity%3A+small%22+label%3A%22role%3A+back+end%2Fdevops%22#column-7198257):
[New Issue Approval](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22complexity%3A+small%22+label%3A%22role%3A+back+end%2Fdevops%22#column-15235217):
ERs: 

Small front end
[Prioritized Backlog](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22complexity%3A+small%22+label%3A%22role%3A+front+end%22#column-7198257):
[New Issue Approval](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22complexity%3A+small%22+label%3A%22role%3A+front+end%22#column-15235217):
ERs: 

Medium backend
[Prioritized Backlog](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22role%3A+back+end%2Fdevops%22+label%3A%22complexity%3A+medium%22#column-7198257): 
[New Issue Approval](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22complexity%3A+medium%22+label%3A%22role%3A+back+end%2Fdevops%22#column-15235217):
ERs: 

Medium front end
[Prioritized Backlog](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22complexity%3A+medium%22+label%3A%22role%3A+front+end%22#column-7198257):  
[New Issue Approval](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22role%3A+front+end%22+label%3A%22complexity%3A+medium%22#column-15235217):
ERs: 

Large backend
[Prioritized Backlog](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22role%3A+back+end%2Fdevops%22+++label%3A%22complexity%3A+large%22#column-7198257): 
[New Issue Approval](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22role%3A+back+end%2Fdevops%22+label%3A%22complexity%3A+large%22#column-15235217):
ERs: 

Large front end
[Prioritized Backlog](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22complexity%3A+large%22+label%3A%22role%3A+front+end%22#column-7198257):
[New Issue Approval](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22complexity%3A+large%22+label%3A%22role%3A+front+end%22#column-15235217): 
ERs: 

Resources/Instructions

@github-actions github-actions bot added Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing labels Mar 26, 2023
@ExperimentsInHonesty

This comment was marked as outdated.

@ExperimentsInHonesty

This comment was marked as outdated.

@ExperimentsInHonesty ExperimentsInHonesty added role: product Product Management Complexity: Medium Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly size: 0.25pt Can be done in 0.5 to 1.5 hours and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing labels Mar 26, 2023
@ExperimentsInHonesty
Copy link
Member Author

ExperimentsInHonesty commented Mar 26, 2023

Full report

Dev Dashboard 2023-03-26

Good First Issue front end & back end
Prioritized Backlog : 6 all are front end and backend)
New Issue Approval: 0
ERs: 0

Good Second Issue front end & back end
Prioritized Backlog: 1 (1 is time sensitive)
New Issue Approval: 1 (time sensitive)
ERs: 0

Small backend
Prioritized Backlog: 4 (2 time sensitive and one is also front end)
New Issue Approval: 1 (time sensitive and is both back and front end)
ERs: 0

Small front end
Prioritized Backlog: 3 (1 is also backend time sensitive)
New Issue Approval: 3 (1 is time sensitive, two will be talked about in the Monday meeting and 1 #4269)
ERs: 2

Medium backend
Prioritized Backlog: 3 (1 which is for dev leads)
New Issue Approval: 2
ERs: 4

Medium front end
Prioritized Backlog: 2 (1 time sensitive)
New Issue Approval: 2 (1 is ready for product)
ERs: 4 (ready for dev lead; one is also front end)

Large backend
Prioritized Backlog: 5
New Issue Approval: 3
ERs: 5

Large front end
Prioritized Backlog: 1
New Issue Approval 2 with the ready for dev lead label
ERs: 0

@ExperimentsInHonesty
Copy link
Member Author

ExperimentsInHonesty commented Mar 26, 2023

Summary of Priorities

Dev Dashboard 2023-03-26

1️⃣ The new front end team members that have finished their good first issue and are ready to start on their second issue will be stalled after the second issue. Because we have just enough for the people already waiting below and there are potentially 9 people who are going to finish their second issue in the next week

Small front end
Prioritized Backlog: 3 (1 is also backend)
New Issue Approval: 3
ERs: 2

Small backend
Prioritized Backlog: 4 (2 time sensitive and one is also front end)
New Issue Approval: 1 (time sensitive and is both back and front end)
ERs: 0

People who need or will need Small issues
- Maria Herzer, @mjh-projects, #3911 (could also do a backend)
- Karen G. Cecena, @karengcecena #4072 (could also do backend) I took an issue away from her because we was not available for 5 days and it was a time sensitive issue - check in on her on 03-29
- Janice Chan, @janice87, #4173 (frontend only, has a pr submitted)
- Drake Nguyen, @drakenguyen4000, #4174 (frontend only has a pr submitted)
- Nicolette Mabeza, @nicolettedmabeza, #3968 (frontend only)


2️⃣ We have 9 people who need good second issues and only a total of 8 issues between good first and good second. And we have an onboarding scheduled for Tuesday. So we probably need at least a total of 30 good first and second issues (15 good first issues would be a good start)

Good First Issue front end & back end

Good Second Issue front end & back end

People who should take up a Good Second Issue next.  
They have all been messaged in their preworks (2023-03-26) to pickup a good first issue if there are no good second issues).
- Aine Fitzgerald, @annierm18, #3709
- Ellen Kellybrew, @EllenKellyb, #3777
- Alejandro Gomez , @agosmou #3787
- Jeristella, @jeristella, #3908
- Phuong Vu, @phuongv8, #3917 
- Victoria Jackson, @neonPurple, #3972
- Luis Sotelo, @LOSjr4 , #4070
- Justin Hang, @hang-justin, #4161
- Devlin Booth, @adevlinb, 4171

3️⃣ We are just a little bit short of issues in prioritized backlog for the people queuing

Medium front end
Prioritized Backlog: 2
New Issue Approval: 2 (1 is ready for product)
ERs: 4 (ready for dev lead)

People waiting for front Medium Front End Issues
- Joshua Juarez, @str-xjua24, #3605 (frontend only)
- Kyra Kwak, @kyrakwak, #3825 (front end only)
- Joy Lu, @jlu9d2, #4073 (front end only)
- Ronald Paek, @ronaldpaek, #4074 (front end only) - off for a week

Also in the list below, because they can do either
- Adaugo Akaluso, @Adaakal, #3782 (frontend or backend)
- Angelina Hayrapetyan, @angieyan, #3813 (frontend or backend)
- Matthew Malane, @mattmalane, #4067 (frontend or backend)
- Jeff Lueck, @jefflueck, #4090 (frontend or backend)


4️⃣ We are just a little bit short of issues in prioritized backlog for the people queuing

Medium backend
There are X people on our team waiting for Medium issues
Prioritized Backlog: 3 (1 of which is for dev leads)
New Issue Approval: 2
ERs: 4

People waiting for Medium backend issue
- Adaugo Akaluso, @Adaakal, #3782 (frontend or backend)
- Angelina Hayrapetyan, @angieyan, #3813 (frontend or backend)
- Matthew Malane, @mattmalane, #4067 (frontend or backend)
- Jeff Lueck, @jefflueck, #4090 (frontend or backend)


5️⃣ We are likely to need more Large frontend issues soon based on the 4 people doing medium issues now who are front end only.

Large front end
Prioritized Backlog: 1
New Issue Approval 2 with the ready for dev lead label
ERs: 0

Large backend
Prioritized Backlog: 5
New Issue Approval: 3
ERs: 5

People ready for Large issues (or about to be)
Kailey Kotynski, @kotynskm, #3778 (frontend or backend)
Cheuk Kay Mary Ng, @maryjng, #3788 (frontend or backend)
Marco Calderon, @mademarc, #3780 (front end only, is working on a medium now)

@ExperimentsInHonesty ExperimentsInHonesty self-assigned this Mar 26, 2023
@ExperimentsInHonesty
Copy link
Member Author

ExperimentsInHonesty commented Mar 27, 2023

Issues to close if no response

Issues to close 30-30

Issues to close 04-02

Responded, check on them in a few days

At message them with the following

Since we have not heard from you.  I am going to go ahead and close this issue.  If you want to return to the website team in the future, feel free to reopen this issue and put it in the in progress column.

@ExperimentsInHonesty ExperimentsInHonesty added frequency: weekly tasks that have to be done every week. Issue never closes size: 1pt Can be done in 4-6 hours role: dev leads Tasks for technical leads and removed size: 0.25pt Can be done in 0.5 to 1.5 hours labels Mar 27, 2023
@ExperimentsInHonesty ExperimentsInHonesty removed their assignment Mar 27, 2023
@roslynwythe
Copy link
Member

roslynwythe commented Apr 4, 2023

@ExperimentsInHonesty
Copy link
Member Author

Full report

Dev Dashboard 2023-04-06

Good First Issue front end & back end
Prioritized Backlog : 20 (19 all also backend)
New Issue Approval: 0
ERs: 0

Good Second Issue front end & back end
Prioritized Backlog: 0
New Issue Approval: 1
ERs: 0

Small backend
Prioritized Backlog: 2
New Issue Approval: 3 (1 is both back and front end)
ERs: 1 (for product)

Small front end
Prioritized Backlog: 7
New Issue Approval: 2 (1 is also front back end)
ERs: 3 (2 for product)

Medium backend
Prioritized Backlog: 2 (1 which is for dev leads)
New Issue Approval: 4
ERs: 1

Medium front end
Prioritized Backlog: 2
New Issue Approval: 1
ERs: 3

Large backend
Prioritized Backlog: 4
New Issue Approval: 3, but (2 are for dev leads only)
ERs: 6

Large front end
Prioritized Backlog: 2
New Issue Approval 4
ERs: 1

@ExperimentsInHonesty

This comment was marked as outdated.

@anjolaaoluwa
Copy link
Member

Good First Issue front end & back end
Prioritized Backlog : 19
New Issue Approval: 4
ERs:0

Small backend
Prioritized Backlog:1
New Issue Approval: 2
ERs: 1

Small front end
Prioritized Backlog:5
New Issue Approval:2
ERs:

Medium backend
Prioritized Backlog:1
New Issue Approval:2
ERs:

Medium front end
Prioritized Backlog:1
New Issue Approval:3
ERs:

Large backend
Prioritized Backlog:3
New Issue Approval:4
ERs:

Large front end
Prioritized Backlog:0
New Issue Approval:3
ERs:

@github-actions
Copy link

github-actions bot commented Jun 2, 2023

@anjolaaoluwa

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Tuesday, May 30, 2023 at 12:15 AM PST.

@github-actions github-actions bot added the To Update ! No update has been provided label Jun 2, 2023
@anjolaaoluwa anjolaaoluwa added Status: Updated No blockers and update is ready for review and removed To Update ! No update has been provided labels Jun 4, 2023
@github-actions github-actions bot added 2 weeks inactive An issue that has not been updated by an assignee for two weeks and removed Status: Updated No blockers and update is ready for review labels Jun 9, 2023
@github-actions
Copy link

github-actions bot commented Jun 9, 2023

@anjolaaoluwa

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Tuesday, June 6, 2023 at 12:16 AM PST.

@roslynwythe
Copy link
Member

Hi @anjolaaoluwa please leave an update on this issue. Thank you.

@github-actions
Copy link

@anjolaaoluwa

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Tuesday, June 13, 2023 at 12:16 AM PST.

@bonniewolfe
Copy link
Member

Why did we close the issue?

@roslynwythe
Copy link
Member

roslynwythe commented Aug 1, 2023

@ExperimentsInHonesty This is fantastic work and it will be very valuable to dev leads, but I noticed that when I select "front end only", the Prioritized Backlog column does not appear. I checked the Project Board and in fact there are no "front end only" issues in the Prioritized Backlog column, but it might be better if the Prioritized Backlog column was displayed even if the number of issues is zero.

Screenshot - "front end only" when no front end only issues exist in Prioritized Backlog. That column is not displayed at all

image

@ExperimentsInHonesty
Copy link
Member Author

@roslynwythe please walk us through that when we see you later today.

@ExperimentsInHonesty
Copy link
Member Author

@roslynwythe can you check this when the dashboard is working again. #6229

@ExperimentsInHonesty ExperimentsInHonesty added Dependency An issue is blocking the completion or starting of another issue and removed ready for product 2 weeks inactive An issue that has not been updated by an assignee for two weeks labels Feb 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Medium Dependency An issue is blocking the completion or starting of another issue Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly frequency: weekly tasks that have to be done every week. Issue never closes role: dev leads Tasks for technical leads role: product Product Management size: 1pt Can be done in 4-6 hours
Projects
Development

No branches or pull requests

4 participants