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

ER: Capitalize Tool Data for green-earth-os.md #5269

Closed
2 of 6 tasks
wanyuguan opened this issue Aug 20, 2023 · 2 comments
Closed
2 of 6 tasks

ER: Capitalize Tool Data for green-earth-os.md #5269

wanyuguan opened this issue Aug 20, 2023 · 2 comments
Labels
Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level ER Emergent Request good first issue Good for newcomers 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) P-Feature: Projects page https://www.hackforla.org/projects/ p-feature: Projects-check We use this page to check to make sure that teams are using the Technology section correctly ready for issue making 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

Comments

@wanyuguan
Copy link
Member

Emergent Requirement - Problem

Tool data in green-earth-os.md needs to be capitalized in order for the Tools filter menu on the projects-check page to render properly.

Issue you discovered this emergent requirement in

Date discovered

2023-08-13

Did you have to do something temporarily

  • YES
  • NO

Who was involved

@wanyuguan @Josiah-O @ExperimentsInHonesty

What happens if this is not addressed

Tools data for GreenEarthOS project will not be displayed correctly in the Tools filter menu on the projects-check page.

Resources

Project Check Page
HfLA Homepage
Projects Page
#4806

Recommended Action Items

  • Make a new issue
  • Discuss with team
  • Let a Team Lead know

Potential solutions [draft]

  • Change
tools:
  - Google sheets
  - Google forms
  - Figma
  - FigJam

to

tools:
  - Google Sheets
  - Google Forms
  - Figma
  - FigJam
@wanyuguan wanyuguan added good first issue Good for newcomers 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) role missing P-Feature: Projects page https://www.hackforla.org/projects/ size: 0.25pt Can be done in 0.5 to 1.5 hours p-feature: Projects-check We use this page to check to make sure that teams are using the Technology section correctly labels Aug 20, 2023
@wanyuguan wanyuguan added this to the 03.02 Onboarding flow milestone Aug 20, 2023
@ShambhavII-Singh

This comment was marked as outdated.

@kimberlytanyh kimberlytanyh added the ER Emergent Request label Sep 10, 2023
@ExperimentsInHonesty ExperimentsInHonesty added Issue Making: Level 2 Make issue(s) from an ER or Epic ready for issue making Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level labels Oct 10, 2023
@t-will-gillis
Copy link
Member

Issue #6020 has been created to address this issue, therefore closing this ER.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level ER Emergent Request good first issue Good for newcomers 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) P-Feature: Projects page https://www.hackforla.org/projects/ p-feature: Projects-check We use this page to check to make sure that teams are using the Technology section correctly ready for issue making 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
Development

No branches or pull requests

6 participants