website Pre-work Checklist: Designer: Jolleen Opula

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 designer on the HfLA website UX team, fill in the following fields as you complete each onboarding item.

Action Items

[x] Meet with team lead to introduce you to the project, introduce you to the GitHub board, and receive your first assignment.
[x] Add yourself to the #hfla-site-ux and #hfla-site Slack channels
[x] Share your Gmail address with the team lead
[x] (Once added to the drive) Add yourself to the team roster.
[x] Confirm with the design lead, that they have added you to the meeting invites and added you to the GitHub team and GitHub repo
[x] Self Assign yourself to this issue (gear in right side panel)
[x] Add this issue to Projects: Project Board (gear in right side panel)
[x] Confirm that team lead has given you login credentials for the team Miro and Figma accounts
[x] Attend weekly team meetings:
- [x] UX weekly team meeting, Wednesday 2:30 pm PST
- [x] All team meeting (UX, Development, Product), Sunday 10am PST
[x] Note regarding weekly team meeting requirements: All website team members are required to attend at least 1 team meeting in a week (held on Wednesdays and Sundays). In case, you are unable in any given week, you should reach out to the design lead. Exceptions to this requirement may be provided on a case-by-case basis. Also, please let the design lead 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.
[x] Review Design_Short Term Goals, Plan, and Tasks
[x] Review the Start Here and Design System pages in Figma
[x] Review the prioritized Backlog to see what Design Issues are available (this will not be the complete list, but will give you some talking points for your conversation with your lead).
[ ] Once you take an 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 text below and put it in the 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.
```
Availability for this week:
My estimated ETA for completing this issue:
```
- [ ] Time spent so far: Copy the question below into a new comment below 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. 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
```

Additional notes:

[ ] 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 with increasing complexity in the following order:
- Good first issue (one per person)
- Good second issue (one 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)
[ ] 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 as a comment on your assigned issue, so it can be easily referred to in the next bullet points
Then, add the issue to the "Design Weekly Meeting Agenda" column of the Project Board so that it can be addressed in the next design meeting
You may also add the label "Status: Help Wanted" so other designers can see it and potentially help answer your question
Lastly, you can post your question in the hfla slack channel and link the issue you're working on, so other volunteers can see and respond

Resources/Instructions

Jul 27 '22 21:07 phuonguvan

Hi @JolleenI, 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 :)

Aug 10 '22 21:08 github-actions[bot]

@phuonguvan did Jolleen leave the team? If so, please add a note to this issue and close it. It will automatically move it to the correct column

Sep 19 '22 22:09 ExperimentsInHonesty

I was away for a family emergency then got covid afterwards but I’ll check out the issue and get it done this week.

On Mon, Sep 19, 2022 at 6:09 PM Bonnie Wolfe @.***> wrote:

@phuonguvan https://github.com/phuonguvan did Jolleen leave the team? If so, please add a note to this issue and close it. It will automatically move it to the correct column

— Reply to this email directly, view it on GitHub https://github.com/hackforla/website/issues/3434#issuecomment-1251619948, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2D5NGSFRAJH65AWQZHDYETV7DQBVANCNFSM543CQ27Q . You are receiving this because you were mentioned.Message ID: @.***>

Sep 19 '22 22:09 JolleenI

@JolleenI

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures (optional): "Add any pictures of the visual changes made to the site so far."