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

Pre-work Checklist: Researcher: Anna Kirstine Schirrer #3380

Closed
12 tasks done
aksanna opened this issue Jul 17, 2022 · 5 comments
Closed
12 tasks done

Pre-work Checklist: Researcher: Anna Kirstine Schirrer #3380

aksanna opened this issue Jul 17, 2022 · 5 comments

Comments

@aksanna
Copy link

aksanna commented Jul 17, 2022

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

  • Add yourself to the #hfla-site-ux and #hfla-site Slack channels
  • Share your Gmail address with the research team lead
  • (once added to the drive) Add yourself to the team roster.
  • Confirm with the research team lead that they have added you to the meeting invites and Github repo
  • Self Assign this issue (gear in right side panel)
  • Add this issue to Projects: Project Board (gear in right side panel)
  • Confirm that the research team lead has given you login credentials for the team Miro and Figma accounts
  • 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
  • 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).
  • Meet with team lead to receive first assignment
  • Once you accept an assignment (issue), please add the following in a comment
Availability for this week:
My estimated ETA for completing this issue:
  • Weekly, please also provide an update on the issue
provide update
1. Progress
2. Blockers
3. Availability
4. ETA

Resources/Instructions

@ExperimentsInHonesty
Copy link
Member

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

@aksanna aksanna self-assigned this Jul 17, 2022
@github-actions
Copy link

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
Copy link
Author

aksanna commented Jul 19, 2022

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

ii. About 12 hours

iii. ETA: First week of August.

@ExperimentsInHonesty
Copy link
Member

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

Will you be coming back in the future?

Please share any feedback you have for us on this issue

@roslynwythe
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

3 participants