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: [Sandarsh] #3253

Closed
8 of 12 tasks
sandarshp opened this issue Jun 15, 2022 · 3 comments
Closed
8 of 12 tasks

Pre-work Checklist: Researcher: [Sandarsh] #3253

sandarshp opened this issue Jun 15, 2022 · 3 comments

Comments

@sandarshp
Copy link
Member

sandarshp commented Jun 15, 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

@github-actions
Copy link

Hi @sandarshp.

Good job adding the required labels for this issue. The merge team will review the issue and add a "Ready for Milestone" label once it is ready for prioritization.

Additional Resources:

@sandarshp sandarshp self-assigned this Jun 15, 2022
@ExperimentsInHonesty
Copy link
Member

Hi @sandarshp

Hi @sandarshp 😃! I noticed that you joined the Hack for LA website team on June 15th but have not finished the Pre-work process or closed any issues.

Will you be coming back? Please let us know so that we can unassign you from this issue if you are not going to work on it.

Do you have feedback for us?

@roslynwythe
Copy link
Member

Hi @sandarshp 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 it into the "In Progress" column. Thank you.

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