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

Create Issues to add new variable github-handle for members in new-schools-today.md #7159

Closed
11 tasks done
Tracked by #5441
roslynwythe opened this issue Jul 31, 2024 · 5 comments
Closed
11 tasks done
Tracked by #5441
Assignees
Labels
Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level epic good first issue Good for newcomers Issue Making: Level 1 Make issues from a template and a spreadsheet 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

Comments

@roslynwythe
Copy link
Member

roslynwythe commented Jul 31, 2024

Prerequisites

  1. You must be a member of Hack for LA to work on an issue. If you have not joined yet, please follow the steps on our Getting Started page.
  2. Please make sure you have read our Hack for LA Contributing Guide before you claim/start working on an issue.

Overview

As developers we need to create issues to update each project team member in new-schools-today.md with a the new github-handle variable, that will eventually replace the github and picture variables, reducing redundancy in the project file.

Action Items

  • For each team member listed in _projects/new-schools-today.md that does not have a variable github-handle, create an issue using the template
  • For each issue:
    • In the title, replace [INSERT MEMBER NAME] with the member's name
    • In the title, replace [INSERT PROJECT FILE] with new-schools-today.md
    • Under Action Items, replace [INSERT MEMBER NAME] with the member's name (in 2 places)
    • Under Action Items, replace [INSERT PROJECT FILE] with new-schools-today.md
    • Under Resources, replace [INSERT-PROJECT-FILE] with new-schools-today.md
    • Under Resources, replace [INSERT-PROJECT-FILENAME-WITHOUT-.MD-EXTENSION] with new-schools-today
    • Apply the following labels: "ready for merge team", "good first issue", "role: front end", "role: back end/devOps", "size: 0.25pt", "P-Feature: Project Info and Page"
    • List the issue number in Epic: Create issues to add github-handle to leadership teams #5441 under Good First Issues
  • When all issues have been created and listed, move this issue to the "Questions/In Review" column of the Project Board, and apply the label "ready for merge team"

Resources/Instructions

https://github.com/hackforla/website/wiki/project.md-file-template
https://jekyllrb.com/
Webpage: https://www.hackforla.org/projects/new-schools-today

@roslynwythe roslynwythe added Feature Missing This label means that the issue needs to be linked to a precise feature label. size: missing role missing Complexity: Missing labels Jul 31, 2024

This comment was marked as outdated.

@ExperimentsInHonesty ExperimentsInHonesty added ready for dev lead Issues that tech leads or merge team members need to follow up on Draft Issue is still in the process of being created 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) epic size: 0.25pt Can be done in 0.5 to 1.5 hours Issue Making: Level 1 Make issues from a template and a spreadsheet Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing Complexity: Missing size: missing labels Sep 3, 2024
@ExperimentsInHonesty

This comment was marked as resolved.

@roslynwythe roslynwythe added Ready for Prioritization and removed Draft Issue is still in the process of being created ready for dev lead Issues that tech leads or merge team members need to follow up on labels Sep 16, 2024
@HackforLABot
Copy link
Contributor

Hi @Sujay-Anantha, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:-
i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?)
ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

@Sujay-Anantha Sujay-Anantha moved this from ERs and epics that are ready to be turned into issues to In progress (actively working) in P: HfLA Website: Project Board Nov 25, 2024
@Sujay-Anantha
Copy link
Member

  1. Monday - Friday
  2. End of the week.

@Sujay-Anantha Sujay-Anantha moved this from In progress (actively working) to Questions / In Review in P: HfLA Website: Project Board Nov 25, 2024
@Sujay-Anantha Sujay-Anantha added the ready for merge team needs a senior review either to do some re writing or to approve it for ready for prioritization label Nov 25, 2024
@ExperimentsInHonesty ExperimentsInHonesty removed the ready for merge team needs a senior review either to do some re writing or to approve it for ready for prioritization label Nov 26, 2024
@ExperimentsInHonesty
Copy link
Member

@Sujay-Anantha Thank you for making the issues. I have confirmed they have been created and am closing this issue.

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 epic good first issue Good for newcomers Issue Making: Level 1 Make issues from a template and a spreadsheet 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
Development

No branches or pull requests

4 participants