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

Onboarding: Olatunji #84

Closed
8 of 10 tasks
Headies opened this issue Feb 11, 2022 · 17 comments
Closed
8 of 10 tasks

Onboarding: Olatunji #84

Headies opened this issue Feb 11, 2022 · 17 comments
Assignees
Labels
feature: onboarding p-feature: guidance guidance for how to make guides role: Product size: 1pt Can be done in 6 hours or less

Comments

@Headies
Copy link
Member

Headies commented Feb 11, 2022

Overview

We need an unbiased review of the gather presentation so that we can improve it.

Additional Details

You will be working on guide during this issue, but the purpose of this issue is to evaluate and improve the Gather Examples and Interview Teams presentation. So any notes you have about the guide you will be making should be noted in the issue related to the Guide you choose.

Action Items

  • Create a google doc, with the name GT: Notes on Gather presentation - Olatunji Lawal in the Gather Examples folder (customize with your name)
  • Add to the notes document as you go, with observations about the Gather Presentation. You will encounter some issues, such as font size or other types of formatting changes, what we are looking for though is material changes to the instructions. For instance, if something could use a screenshot to make it clearer, and it doesn't have one or when you try to follow the steps, something is missing.
  • Review the Presentation for Gathering Examples
  • Pick a guide
    • Note the Name of guide and URL of the guide in the comments below
  • Use the presentation to work on the guide
    • Leaving comments in the presentation if you have a suggested improvement
    • Putting any notes about the guide either in the guide or in the issue for the guide (as appropriate)
  • Clean up your presentation notes
  • Present to the Guides Team

Resources/Instructions

@Headies Headies added role: Product p-feature: guidance guidance for how to make guides size: 1pt Can be done in 6 hours or less labels Feb 11, 2022
@Headies Headies self-assigned this Feb 11, 2022
@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Feb 18, 2022

Please provide update

  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."
    Availability: "How much time will you have this week to work on this issue?"
  3. Availability
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (if necessary): "Add any pictures that will help illustrate what you are working on."

@Headies
Copy link
Member Author

Headies commented Feb 18, 2022

  1. Progress:
    i. Created a document and picked a guides to work on.
    ii. Moved the assigned guides to "in progress"
  2. Blockers: personal for now and making observations for further clarity.
  3. Availability: 2hours
  4. ETA: Wednesday

@Headies
Copy link
Member Author

Headies commented Feb 23, 2022

Progress: added my observation to my google doc
ETA: Monday
Blockers: personal reasons

@Headies
Copy link
Member Author

Headies commented Mar 7, 2022

Progress: Observations documented and ready to be reviewed

@ExperimentsInHonesty
Copy link
Member

We can't make a video because we don't have a finished set of slides. We can readdress this after the slides are done.

@Headies
Copy link
Member Author

Headies commented Mar 9, 2022

Progress: SLides to be revisited for further review
Blockers: personal
ETA: 14th of March

@ExperimentsInHonesty
Copy link
Member

@Headies Please provide update

  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 (if necessary): "Add any pictures that will help illustrate what you are working on."

@Headies
Copy link
Member Author

Headies commented Mar 16, 2022

Progress: I still have to go over the presentation.
Availability: My time is limited due to personal reasons
ETA: I will need a week break. The change in meeting schedule is not working for me atm

@ExperimentsInHonesty
Copy link
Member

@Headies Thanks for the response. I am not exactly clear on how to handle the issue. Are we talking a week break, or month, etc? Can you give us an ETA on the break, so I know the next action to take.

@Headies
Copy link
Member Author

Headies commented Mar 18, 2022

A week break. I will be back to the team on the 29th of this month.

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Mar 23, 2022

Check back in on them on 2022-03-30

@ExperimentsInHonesty
Copy link
Member

@Headies
Please provide update

  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 (if necessary): "Add any pictures that will help illustrate what you are working on."

@ExperimentsInHonesty
Copy link
Member

@Headies
Please provide update

  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 (if necessary): "Add any pictures that will help illustrate what you are working on."

Next message to be sent on 2022-04-12

@ExperimentsInHonesty
Copy link
Member

@Headies We did not hear from you last week after we reached out, please provide the following update in this issue.

  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 (if necessary): "Add any pictures that will help illustrate what you are working on."

If we do not hear from you in the next week, you will be removed from the project, until you are ready to come back.

@ExperimentsInHonesty
Copy link
Member

sent a message in slack. Send a week 3 message on 2022-04-20

@Headies
Copy link
Member Author

Headies commented Apr 18, 2022

Hi Bonnie,

Sorry, I have not responded in weeks.

I have been swamped with work and the meeting schedule clashes with my work hours.

I'd hope to be back on the team in no time.

Regards

@ExperimentsInHonesty
Copy link
Member

@Headies Its been over a month. I was really clear during onboarding that if you don't have the time to volunteer at Hack for LA (minimum 6 hours a week) then you should not volunteer here. So while I understand not being able to make this meeting time. You could be working on the issue asynchronously, but you are not doing that either. It's using up time every meeting to check on you and your issue. I am going to remove you from the team. If you want to join us again, please reach out in the team Slack channel when you have time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature: onboarding p-feature: guidance guidance for how to make guides role: Product size: 1pt Can be done in 6 hours or less
Projects
Development

No branches or pull requests

2 participants