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: Funke Olatunbosun #93

Closed
7 of 12 tasks
Funmikee opened this issue Mar 9, 2022 · 21 comments
Closed
7 of 12 tasks

Onboarding: Funke Olatunbosun #93

Funmikee opened this issue Mar 9, 2022 · 21 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

@Funmikee
Copy link
Member

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

This comment was marked as outdated.

@ExperimentsInHonesty

This comment was marked as outdated.

@Funmikee

This comment was marked as outdated.

@ExperimentsInHonesty
Copy link
Member

Q: A quick question, the gathered examples can be for any type of partner outreach, correct?
A: Yes, every type of partner outreach is appropriate for the guide

@ExperimentsInHonesty

This comment was marked as outdated.

@Funmikee

This comment was marked as outdated.

@ExperimentsInHonesty
Copy link
Member

@Funmikee thanks for the update. Hope your trip was good

@Funmikee
Copy link
Member Author

@Funmikee thanks for the update. Hope your trip was good

Thanks, Bonnie, my trip was great just down with fever due to a change of environment.

@Funmikee

This comment was marked as outdated.

@ExperimentsInHonesty

This comment was marked as outdated.

@Funmikee

This comment was marked as off-topic.

@SheIsBukki

This comment was marked as outdated.

@Funmikee
Copy link
Member Author

Progress: I've finished searching for all projects, I'll start sending Slack messages to the project team members where I couldn't find any assets.
Blockers: How do I contact a few projects that have no assets and do not have a Slack channel?
Availability: 3-5 hours

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Mar 30, 2022

@Funmikee All the projects except Civic Tech Structure do have channels. Check Hackforla.org for the ones you are missing.

Review the BOP project issues tab again, you are missing some outreach messaging there. Interestingly enough, that's the project I use most as a model for other project's messaging. Followed by the Internship project.

@ExperimentsInHonesty
Copy link
Member

@Funmikee It looks like you are making good progress looking through the project's slack channels. During the next meeting you attend, let's review the issues you have raised in this document GT: Notes on Gather Presentation - Funke Olatunbosun to see if we can resolve them.

@ExperimentsInHonesty
Copy link
Member

@Funmikee will you be able to make a meeting soon?

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Apr 13, 2022

Send 2 week message on 2022-04-15

@ExperimentsInHonesty
Copy link
Member

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

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

Check this issue on 2022-04-22. If no response, send 3 week message

@SheIsBukki
Copy link
Member

@Funmikee We have not heard from you via this issue or slack for 3 full weeks. We are going to remove you from the team resources You are welcome to come back, when you are ready, you can message us in the #guide Slack channel to be re-added.

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