Pre-work Checklist: Researcher: Anna Kirstine Schirrer

[aksanna]

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

Action Items

• [x] Add yourself to the #hfla-site-ux and #hfla-site Slack channels
• [x] Share your Gmail address with the research team lead
• [x] (once added to the drive) Add yourself to the team roster.
• [x] Confirm with the research team lead that they have added you to the meeting invites and Github repo
• [x] Self Assign this issue (gear in right side panel)
• [x] Add this issue to Projects: Project Board (gear in right side panel)
• [x] Confirm that the research team lead has given you login credentials for the team Miro and Figma accounts
• [x] Attend weekly team meetings:
  • UX weekly team meeting, Thursdays 5 pm PST
  • All team meetings (UX, Development, Product), Sunday 10 am PST
  • Research team meetings, Wednesdays, 2:00 pm PST
• [x] Review the prioritized backlog to see what Research Issues are available (this will not be the complete list, but will give you some talking points for your conversation with your lead).
• [x] Meet with team lead to receive first assignment
• [x] Once you accept an assignment (issue), please add the following in a comment

Availability for this week:
My estimated ETA for completing this issue:

• [x] Weekly, please also provide an update on the issue

provide update
1. Progress
2. Blockers
3. Availability
4. ETA

Resources/Instructions

• Project Board filtered to show role: user research
• Miro
• Figma
• Googledrive-UI/UX
• Googledrive-HackforLA website
• UX Research Presentations
• Weekly Meeting Agendas
• Example of an issue with really good updates, this issue also is a good example of when you have finished an issue, but there is still more work to be done, so it leads to a new issue being made instead of changing the scope of the original issue.

[ExperimentsInHonesty]

After you are added to the roster, @vaisali89 will add you to these teams, and then you can self assign this issue https://github.com/orgs/hackforla/teams/website/members https://github.com/orgs/hackforla/teams/website-write/members

[github-actions[bot]]

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

[aksanna]

i. Availability: July 19 + 21, 26 + 27, August 2 + 3

ii. About 12 hours

iii. ETA: First week of August.

[ExperimentsInHonesty]

Message: Hi @aksanna 😃! I noticed that you joined the Hack for LA website team on July 17th and have not had any activity since July 24, 2022

• I have unassigned you from #2706

Will you be coming back in the future?

Please share any feedback you have for us on this issue

[roslynwythe]

Hi @aksanna we are closing this issue because we have not heard from you in almost a year, but if you are interested in participating in Hack for LA in the future, you are welcome to reopen this issue, leave an update, and move the issue into the "In Progress" column.