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: Isaiah Ozadhe #97

Closed
7 of 12 tasks
Tekkieware opened this issue Mar 16, 2022 · 17 comments
Closed
7 of 12 tasks

Onboarding: Isaiah Ozadhe #97

Tekkieware opened this issue Mar 16, 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

@Tekkieware
Copy link
Member

Tekkieware commented Mar 16, 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.

  • Any notes you have about the guide you will be making should be noted in the issue related to the Guide you choose.
  • Any notes about the Gather Examples and Interview Teams presentation should be in the document you create.

Action Items

  • Create a Google doc, with the name GT: Notes on Gather presentation - YOUR NAME HERE in the Gather Examples folder (customize with your name)
    • Add the link to the document and its name in the Resources section below
  • 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.
    • If while looking at the presentation (not the guide), you encounter any words that you think should be added to our glossary, please add them to the Glossary issue as comments.
  • 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

When you do your update please provide

  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."
@Tekkieware Tekkieware added role: Product p-feature: guidance guidance for how to make guides size: 1pt Can be done in 6 hours or less feature: onboarding labels Mar 16, 2022
@Tekkieware Tekkieware self-assigned this Mar 16, 2022
@ExperimentsInHonesty
Copy link
Member

@Tekkieware
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."

@Tekkieware
Copy link
Member Author

Tekkieware commented Mar 21, 2022

@ExperimentsInHonesty
Progress: Done with tasks 1 to 5
Blockers: None
Availability: Not exactly sure.
ETA: I can't tell for now because the next part(picking and working on a guide) is still a bit hazy to me.
Pictures (if necessary): None.

@ExperimentsInHonesty
Copy link
Member

Hi @Tekkieware, I was just explaining to the team how it's hard to do ETAs when you don't know the full picture, and even then it can be hard. Your update communicated that perfectly. Thanks for the update.

@SheIsBukki
Copy link
Member

We looked at @Tekkieware's observations and resolved some of them

@ExperimentsInHonesty
Copy link
Member

@Tekkieware 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

@Tekkieware 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 2022-04-15

@Tekkieware
Copy link
Member Author

Tekkieware commented Apr 5, 2022

@ExperimentsInHonesty
Progress: Still on gathering examples for my guide. Checked about 12 projects so far(their wiki, slack, issues, project board and sometimes readme and contributing.md files). 12 more projects left unchecked.
Blockers: Not finding much information related to git or version control except for projects that have contributing.md files.
Availability: Not exactly sure.
ETA: Should be able to finish gathering examples before the week runs out.
Pictures (if necessary): None.

@ExperimentsInHonesty
Copy link
Member

@Tekkieware
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

@Tekkieware

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

If no response, send 3 week message on 2022-04-25

@Tekkieware
Copy link
Member Author

@ExperimentsInHonesty I'm really sorry for not updating earlier. Something came up and I'll be away one more week.

@SheIsBukki
Copy link
Member

@Tekkieware Okay, good to hear from you.

We will check back on 2022-05-02

@ExperimentsInHonesty
Copy link
Member

@Tekkieware Please provide update. It's been 27 days since your last progress report. Do you want to be removed from the team? If not, please make time for your tasks. As I communicated during onboarding. Hack for LA requires 6 hours a week to be on a project team.

  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

@Tekkieware
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

remove on 5/11

@Tekkieware
Copy link
Member Author

@ExperimentsInHonesty
I think i have to step aside for a while. I have a lot going on and i'm struggling to keep up. I'll be back soon. My sincere apologies.

@ExperimentsInHonesty
Copy link
Member

@Tekkieware Thanks for letting us know. Reach out in the Slack channel anytime you are ready to come back.

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

3 participants