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

Roll Out: Refactor GitHub handle in project files #5440

Open
2 of 46 tasks
roslynwythe opened this issue Sep 4, 2023 · 2 comments
Open
2 of 46 tasks

Roll Out: Refactor GitHub handle in project files #5440

roslynwythe opened this issue Sep 4, 2023 · 2 comments
Labels
Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level Dependency An issue is blocking the completion or starting of another issue Issue Making: Level 5 Make a Rollout Plan that has >1 epics to achieve and timelines for interdependencies 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 size: 0.25pt Can be done in 0.5 to 1.5 hours
Milestone
x. Technical debt

Comments

@roslynwythe
Copy link
Member

roslynwythe commented Sep 4, 2023 •
edited by ExperimentsInHonesty
Loading

Dependency

Overview

We need to define a single variable github-handle to hold the github handle for each member of the leadership team, to replace the github and picture variables which both hold urls that contain the github handle. Afterwards, the code displaying the leadership team can be modified to use the new variable, and the variables github and picture can be removed.

Files

  • 100-automations.md
  • 311-data.md
  • access-the-data.md
  • adopt-civic-art.md
  • ballot-nav.md
  • brigade-organizers-playbook.md
  • civic-opportunity-project.md
  • civic-tech-index.md
  • civic-tech-jobs.md
  • civic-tech-structure.md
  • criminal-sentencing.md
  • curbmap.md
  • design-systems.md
  • ms-triage-tracker.md
  • engage.md
  • expunge-assist.md
  • food-oasis.md
  • green-earth-os.md
  • guides-team.md
  • heart.md
  • hellogov.md
  • home-unite-us.md
  • jobs-for-hope.md
  • light-the-way.md
  • lucky-parking.md
  • metro-ontime.md
  • new-schools-today.md
  • not-today.md
  • open-community-survey.md
  • public-tree-map.md
  • shared-housing-project.md
  • spare.md
  • tdm-calculator.md
  • tech-work-experience.md
  • undebate.md
  • vrms.md
  • website.md
  • work-for-la.md
  • writeforall.md
  • youthjusticenav.md
  • assets\js/project.js

Roll Out Plan

After the above issues are all closed:

  • Create Issue: Modify code that displays the leadership team to use the new github-handle variable

After the above issues are all closed:

  • Create issues to remove the github and picture variables.

Resources/Instructions

https://github.com/hackforla/website/wiki/project.md-file-template
https://jekyllrb.com/
@roslynwythe roslynwythe added 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 5 Make a Rollout Plan that has >1 epics to achieve and timelines for interdependencies Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level labels Sep 4, 2023
@roslynwythe roslynwythe added Ready for Prioritization and removed Draft Issue is still in the process of being created labels Sep 17, 2023
@wanyuguan

This comment was marked as outdated.

Sign in to view
@wanyuguan wanyuguan added ready for product ready for dev lead Issues that tech leads or merge team members need to follow up on and removed Ready for Prioritization ready for product labels Sep 17, 2023
@wanyuguan wanyuguan added this to the x. Technical debt milestone Sep 17, 2023
@roslynwythe roslynwythe mentioned this issue Sep 18, 2023
Open
2 tasks
@roslynwythe roslynwythe removed the P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) label Sep 23, 2023
@roslynwythe

This comment was marked as resolved.

Sign in to view
@Josiah-O Josiah-O added the Feature Missing This label means that the issue needs to be linked to a precise feature label. label Sep 24, 2023
@ExperimentsInHonesty ExperimentsInHonesty added the P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) label Sep 24, 2023
@roslynwythe roslynwythe removed the Feature Missing This label means that the issue needs to be linked to a precise feature label. label Oct 8, 2023
@ExperimentsInHonesty ExperimentsInHonesty removed the ready for dev lead Issues that tech leads or merge team members need to follow up on label May 7, 2024
@ExperimentsInHonesty ExperimentsInHonesty added the Dependency An issue is blocking the completion or starting of another issue label Jun 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level Dependency An issue is blocking the completion or starting of another issue Issue Making: Level 5 Make a Rollout Plan that has >1 epics to achieve and timelines for interdependencies 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 size: 0.25pt Can be done in 0.5 to 1.5 hours
Projects
P: HfLA Website: Project Board
Status: Ice box
Milestone
x. Technical debt
Development

No branches or pull requests
4 participants
@roslynwythe @wanyuguan @ExperimentsInHonesty @Josiah-O