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: Jackie Riley #2500

Closed
10 tasks done
JackieRiley1 opened this issue Nov 17, 2021 · 8 comments
Closed
10 tasks done

Pre-work Checklist: Researcher: Jackie Riley #2500

JackieRiley1 opened this issue Nov 17, 2021 · 8 comments
Assignees
Labels
Complexity: Prework prework feature: research plan any issue that is specifically about the overall research, not a subtask feature: research role: user research size: missing Status: Updated No blockers and update is ready for review

Comments

@JackieRiley1
Copy link

JackieRiley1 commented Nov 17, 2021

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
  • 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, Mondays, 11:30 am 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

Project Board filtered to show role: user research
Miro
Figma
Googledrive-UI/UX
Googledrive-HackforLA website
UX Research Presentations
Weekly Meeting Agendas

@github-actions github-actions bot added Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing size: missing labels Nov 17, 2021
@JackieRiley1 JackieRiley1 self-assigned this Nov 17, 2021
@macho-catt macho-catt changed the title Pre-work Checklist: Researcher: Jackie Riley] Pre-work Checklist: Researcher: Jackie Riley Nov 18, 2021
@macho-catt macho-catt added Feature: Onboarding/Contributing.md good first issue Good for newcomers role: user research and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing size: missing labels Nov 18, 2021
@JackieRiley1
Copy link
Author

Availability for this week: Tues, Wed, Thurs
My estimated ETA for completing this issue: 2 hours

@ExperimentsInHonesty
Copy link
Member

@JackieRiley1 Please see this issue for instructions about how to do updates every week on your issue. Once you have done that two weeks in a row then you can close this issue. Remember to provide an overall ETA for completion and on the next issue you work on, do that when you first self assign.

@github-actions
Copy link

@JackieRiley1

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.

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

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

You are receiving this comment because your last comment was before Monday, January 24, 2022 at 11:18 PM PST.

@ExperimentsInHonesty
Copy link
Member

@JackieRiley1 I do not see that you are putting updates, as prescribed above, in the issue you are working on. Please re-read the guidance in this issue for how to communicate on the team effectively.

@github-actions
Copy link

@JackieRiley1

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.

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

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

You are receiving this comment because your last comment was before Tuesday, March 15, 2022 at 12:19 AM PST.

@phuonguvan
Copy link
Member

@JackieRiley1 Hey! This is the design team lead and I was wondering if you are still working on this project. Bonnie told me to update you guys so let me know as soon as possible!

@JackieRiley1
Copy link
Author

JackieRiley1 commented Mar 24, 2022 via email

@github-actions github-actions bot added Status: Updated No blockers and update is ready for review and removed 2 weeks inactive labels Mar 25, 2022
@ExperimentsInHonesty ExperimentsInHonesty added prework and removed good first issue Good for newcomers labels Apr 3, 2022
@ExperimentsInHonesty
Copy link
Member

@JackieRiley1 sorry for the confusion. Phu was checking in on your because we have not gotten updates from you on this issue... but this issue should have been closed. Sorry for the mixup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Prework prework feature: research plan any issue that is specifically about the overall research, not a subtask feature: research role: user research size: missing Status: Updated No blockers and update is ready for review
Projects
Development

No branches or pull requests

6 participants