Skip to content

Skills Issue: Developer: Danielle Aras #6948

Open
Open
Skills Issue: Developer: Danielle Aras#6948
Assignees
daras-cu
Labels
Complexity: PreworkpreworkFeature: Onboarding/Contributing.mdSkills Issue CompletedSkills Template status: UPDATEDrole: back end/devOpsTasks for back-end developersrole: front endTasks for front end developerssize: 1ptCan be done in 4-6 hours
Milestone
08. Team workflow

Description

@daras-cu
daras-cu
opened on Jun 4, 2024

Prerequisite

We are looking forward to having you on our team. Please make sure to attend the general Hack for LA onboarding to get the process started https://meetup.com/hackforla/events.

Overview

As a new developer on the HfLA website team, fill in the following fields as you complete each onboarding item.

Special Notes

  1. It may take you a few weeks to finish this issue, because part of it is learning how to provide updates on issues that take more than a week to complete. Please keep this issue open until you have been able to do all the steps.
  2. Usually we don't want to you have more than one issue assigned to you at a time, this issue is the exception, because it is instructions on how to work on other issues.
  3. The action items listed below should mostly be worked on in a sequential order. However, you don't have to wait on one if you can proceed with the others, For instance, you don't have to wait for attending a weekly meeting before setting up your dev environment.

Action Items

  • Add yourself to the #hfla-site and #hfla-site-pr Slack channels
    • To find contact information for the merge team members and technical leads, please take a look at our Meet the Team wiki page
  • Add yourself to the team roster
  • After you have finished adding yourself to the roster, let a merge team member or a technical lead know you have added yourself to the roster and would like to be added to the website-write and website teams on GitHub
  • Self Assign this issue (gear in right side panel)
  • Add the "role: front end" or "role: back end" or both label(s) to this issue and remove the "role missing" label (gear in right side panel)
  • Add this issue to the Project Board under the Projects section (gear in right side panel)
  • Signup for a Figma account
  • Attend weekly team meetings:
    • Developer (front-end/back-end) weekly team meeting, Tuesdays 7-8pm PST
    • (Optional) Office Hours, Thursdays 7-8pm PST
    • All team meeting (UX, Development, Product), Sunday 10am-12pm PST
  • Note: There are no meetings on the 1st-7th of every month.
  • Note regarding weekly team meeting requirements: All website team members are required to attend at least 1 team meeting in a week (held on Tuesdays, Thursdays and Sundays). In case, you are unable in any given week, you should reach out to the tech leadership team. Exceptions to this requirement may be provided on a case-by-case basis. Also, please let the tech leadership team know (through a slack message in the hfla-site channel as well as an @ mention in a comment of the issue that you would be working on) if you are planning to take a week off or a longer vacation.
  • Complete steps 1.1 - 1.6 in Part 1: Setting up the development environment within Contributing.md
  • Read section 2.1 - 2.4 in Part 2: How the Website team works with GitHub issues within Contributing.md
  • Once you take a good first issue, you will provide estimates and progress reports. Also, once you finish providing your "Estimate" action item below, please answer the question in the "Time spent so far" action item (also below).
    • Estimate: Copy the below and put it in the "good first issue" that you picked.
      Check this box when you have completed this task so that we can identify if you understood the instructions and know what to do on all subsequent issues upon assignment. (Note: Please provide estimates on all the issues that you pick up, going forward.)
    Availability for this week:
My estimated ETA for completing this issue:
    • Time spent so far: Copy the question below into a new comment below (in this pre-work issue only) and answer it. This is just to get feedback on how long it took you to get to this point on this pre-work. There is no right or wrong answers. There is no judgement. It is ok if you take a long time or if you do it really fast or at any pace.
    How many hours did it take you to finish the pre-work up to and including adding your initial ETA and availability for your good first issue, including attending your first meetings?
    • Progress Reports: Copy the below and put it in the issue once you have been assigned to the issue at least 5 days (we check weekly on Fridays), or sooner if you have something to report. If you finish this issue before 5 days are reached, Yeah!!, do it on your next issue. This update should be done every week for every issue that you are assigned to. The checkbox here is meant for us to see if you understood the instructions when you end up doing your first weekly progress update.
    Provide Update
1. Progress
2. Blockers
3. Availability
4. ETA
  • Read sections 3.1.a - 3.1.c in 3.1 How to make a pull request to learn more about how to make a pull request (PR) for the issue that you are working on and how to make changes to your PR if changes are requested by the reviewer
  • Additional notes:
    • Please don't forget to review pull requests whenever you are able to. The How to review Pull Requests guide will teach you how to review pull requests.
    • Please work on only one issue at a time and wait until your pull request is merged before picking up another issue.
  • Read and understand how we progress through issues. Then, you can check this off.
    Progress through issues in the prioritized backlog only with increasing complexity in the following order:
    • Good first issue (two per person)
    • Small (one per person, with some exceptions, see below)
    • Medium (you can work on more than one medium issue, but only one at a time)
    • Large (you can work on more than one large issue, but only one at a time)
      • The reasons for this progression are:
        • The issues start out as being prescriptive and become less so as you gain more experience by working through increasingly complex issues.
        • We are trying to teach you the team methodology through the issues themselves.
        • It ensures you understand what we expect and the quality of contributions.
      • You can work on back-to-back small issues if it meets the following criteria:
        • You are learning something new and need to work on an issue of a lesser complexity
        • Special request by a lead or pm
  • Read the Start Here - Developers in Figma
  • Go familiarize yourself with the Hack for LA Design System page in Figma (where you can see components and their SCSS classes)
  • Once all tasks are completed, close this issue. This issue will remain open until you get through your first progress report. Once you have done that, we are confident you know how to keep the momentum going on your issue and keep your team informed.

What should I do if I have a question about an issue I'm working on, and I haven't gotten a response yet?

  • First, you should post the question or blocker as a comment on your assigned issue, so it can be easily referred to in the next bullet points.
  • Then, add the label "Status: Help Wanted" so other developers can see it and potentially help answer your question. In addition, you will still need to post a Slack message or bring it up in meeting so we know you need help; see below for how to do that.
  • Also, you can post your question on the hfla-site slack channel and link the issue you're working on, so other developers can see and respond.
  • Lastly, you can add the issue to the "Development team meeting discussion items" column of the Project Board so that it can be addressed in the next development meeting. Please bring it during the meeting that you need help.

Resources/Instructions

Activity

  1. daras-cu
    added
    Feature: Onboarding/Contributing.md
    size: 1ptCan be done in 4-6 hours
    Complexity: Preworkprework
    role missing
    on Jun 4, 2024

  2. github-actions commented on Jun 4, 2024

    @github-actions
    github-actionsbot
    on Jun 4, 2024 – with GitHub Actions · Hidden as outdated
  3. daras-cu
    self-assigned this
    on Jun 4, 2024
  4. daras-cu
    added
    role: front endTasks for front end developers
    role: back end/devOpsTasks for back-end developers
    and removed
    role missing
    on Jun 4, 2024
  5. roslynwythe
    added this to the 08. Team workflow milestone on Jun 4, 2024

  6. daras-cu commented on Jun 10, 2024

    @daras-cu
    daras-cu
    on Jun 10, 2024
    MemberAuthor

    How many hours did it take you to finish the pre-work up to and including adding your initial ETA and availability for your good first issue, including attending your first meetings?
    Approximately 6.5 hours

  7. ExperimentsInHonesty
    added
    role: back end
    on Jun 18, 2024
  8. ExperimentsInHonesty
    added this to P: HfLA Website: Project Boardon Jun 23, 2024
  9. ExperimentsInHonesty
    moved this to In progress (actively working) in P: HfLA Website: Project Boardon Jun 23, 2024

  10. github-actions commented on Jun 28, 2024

    @github-actions
    github-actionsbot
    on Jun 28, 2024 – with GitHub Actions · Hidden as outdated

  11. 93 remaining items

  12. HackforLABot commented on Jun 6, 2025

    @HackforLABot
    HackforLABot
    on Jun 6, 2025 · Hidden as outdated

  13. HackforLABot commented on Jun 13, 2025

    @HackforLABot
    HackforLABot
    on Jun 13, 2025 · Hidden as outdated

  14. HackforLABot commented on Jun 20, 2025

    @HackforLABot
    HackforLABot
    on Jun 20, 2025 · Hidden as outdated

  15. HackforLABot commented on Jun 27, 2025

    @HackforLABot
    HackforLABot
    on Jun 27, 2025 · Hidden as outdated

  16. HackforLABot commented on Aug 1, 2025

    @HackforLABot
    HackforLABot
    on Aug 1, 2025 · Hidden as outdated

  17. HackforLABot commented on Aug 10, 2025

    @HackforLABot
    HackforLABot
    on Aug 10, 2025
    Contributor

    Activity Log: daras-cu

    Repo: https://github.com/hackforla/website

    ⚠ Important note: The bot updates this comment automatically - do not edit
  18. t-will-gillis
    added
    Skills Issue Completed
    and removed
    status: 2 Weeks InactiveAn issue that has not been updated by an assignee for two weeks
    on Aug 12, 2025
  19. HackforLABot
    added
    status: 2 Weeks InactiveAn issue that has not been updated by an assignee for two weeks
    on Aug 15, 2025

  20. HackforLABot commented on Aug 15, 2025

    @HackforLABot
    HackforLABot
    on Aug 15, 2025 · Hidden as outdated
  21. t-will-gillis
    removed
    status: 2 Weeks InactiveAn issue that has not been updated by an assignee for two weeks
    on Aug 17, 2025
  22. HackforLABot
    added
    status: 2 Weeks InactiveAn issue that has not been updated by an assignee for two weeks
    on Aug 22, 2025

  23. HackforLABot commented on Aug 22, 2025

    @HackforLABot
    HackforLABot
    on Aug 22, 2025 · Hidden as outdated

  24. HackforLABot commented on Aug 29, 2025

    @HackforLABot
    HackforLABot
    on Aug 29, 2025 · Hidden as outdated
  25. t-will-gillis
    removed
    status: 2 Weeks InactiveAn issue that has not been updated by an assignee for two weeks
    on Feb 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Complexity: PreworkpreworkFeature: Onboarding/Contributing.mdSkills Issue CompletedSkills Template status: UPDATEDrole: back end/devOpsTasks for back-end developersrole: front endTasks for front end developerssize: 1ptCan be done in 4-6 hours

Type

No type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions