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

Epic: Create issues to add github-handle to leadership teams #5441

Open
Tracked by #5440
roslynwythe opened this issue Sep 4, 2023 · 30 comments
Open
Tracked by #5440

Epic: Create issues to add github-handle to leadership teams #5441

roslynwythe opened this issue Sep 4, 2023 · 30 comments
Assignees
@roslynwythe
Labels
2 weeks inactive An issue that has not been updated by an assignee for two weeks Complexity: Medium Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level epic Issue Making: Level 2 Make issue(s) from an ER or Epic P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 0.25pt Can be done in 0.5 to 1.5 hours
Milestone
08. Team workflow

Comments

@roslynwythe
Copy link
Member

roslynwythe commented Sep 4, 2023 •
edited by t-will-gillis
Loading

Overview

We need to create issues to define a single variable to hold the github handle for each member of the leadership team. Eventually, this variable will replace the existing github and picture variables, reducing redundancy in the project data.

"Good First Issues"

Issue Making Level 1 Issues

Action Items

Resources/Instructions

https://github.com/hackforla/website/wiki/project.md-file-template
https://jekyllrb.com/
Spreadsheet with all the project.md files
@roslynwythe roslynwythe added role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) Draft Issue is still in the process of being created size: 0.25pt Can be done in 0.5 to 1.5 hours Issue Making: Level 2 Make issue(s) from an ER or Epic Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level labels Sep 4, 2023
@roslynwythe roslynwythe changed the title Epic: Create issues to add github-handle to leadership Epic: Create issues to add github-handle to leadership teams Sep 4, 2023
@roslynwythe

This comment was marked as outdated.

Sign in to view
@roslynwythe

This comment was marked as outdated.

Sign in to view
@roslynwythe roslynwythe mentioned this issue Sep 12, 2023
Closed
6 tasks
@roslynwythe roslynwythe self-assigned this Sep 12, 2023
@github-actions

This comment has been minimized.

Sign in to view
@roslynwythe roslynwythe added Ready for Prioritization ready for product and removed Draft Issue is still in the process of being created Ready for Prioritization labels Sep 12, 2023
@roslynwythe
Copy link
Member Author

roslynwythe commented Sep 12, 2023 •
edited
Loading

@ExperimentsInHonesty please review the template or alteratively the sample issue #5504

This was referenced Sep 12, 2023
Closed
Closed
Closed
Closed
Closed
Closed
Open
Open
Closed
@wanyuguan wanyuguan added this to the 08. Team workflow milestone Sep 17, 2023
This was referenced Sep 5, 2024
Open
Open
Closed
@HackforLABot

This comment has been minimized.

Sign in to view
This was referenced Sep 10, 2024
Open
Open
Open
Open
Open
Open
@HackforLABot

This comment has been minimized.

Sign in to view
@DrAcula27 DrAcula27 mentioned this issue Sep 14, 2024
Closed
5 tasks
@8alpreet 8alpreet mentioned this issue Sep 16, 2024
Open
@HackforLABot

This comment has been minimized.

Sign in to view
@HackforLABot

This comment has been minimized.

Sign in to view
@HackforLABot
Copy link
Contributor

@roslynwythe

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 Questions/In Review column of the Project Board 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, October 8, 2024 at 12:05 AM PST.

@HackforLABot
Copy link
Contributor

@roslynwythe

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 Questions/In Review column of the Project Board 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, October 15, 2024 at 12:04 AM PST.

This was referenced Nov 25, 2024
Open
Open
Open
Open
This was referenced Nov 29, 2024
Open
Open
This was referenced Dec 4, 2024
Open
Open
Open
This was referenced Dec 13, 2024
Open
Open
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@roslynwythe roslynwythe

Labels
2 weeks inactive An issue that has not been updated by an assignee for two weeks Complexity: Medium Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level epic Issue Making: Level 2 Make issue(s) from an ER or Epic P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 0.25pt Can be done in 0.5 to 1.5 hours
Projects
P: HfLA Website: Project Board
Status: In progress (actively working)
Milestone
08. Team workflow
5 participants
@roslynwythe @wanyuguan @ExperimentsInHonesty @t-will-gillis @HackforLABot