Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Mentored Sprints 2022 - kickoff

Mentored Sprints 2022 - kickoff

Tania Allard

April 30, 2022
Tweet

More Decks by Tania Allard

Other Decks in Technology

Transcript

  1. @MentoredSprints mentored-sprints.dev
 All in local times • 2:00 pm -

    Kick off • 2:30 pm - Sprints start (roughly) • 3:45-4:15 pm - Afternoon break • 5:45 pm Wrap up • 6:00 pm End Schedule https://bit.ly/mentoredsprints-22
  2. @MentoredSprints mentored-sprints.dev
 Code of conduct We want every attendee to

    feel welcome and have an enjoyable, fulfilling experience at PyCon, even in a virtual event. Please familiarize yourself with PyCon’s Code of Conduct and Attendee Procedure For Reporting Code of Conduct Incidents: https://us.pycon.org/2022/about/code-of-conduct/ Report any incidents to [email protected] https://bit.ly/mentoredsprints-22
  3. @MentoredSprints mentored-sprints.dev
 Build a community Give back to open source

    Empower folks and support dei efforts Our goals https://bit.ly/mentoredsprints-22
  4. @MentoredSprints mentored-sprints.dev
 In a nutshell The Turing Way project illustration

    by Scriberia. Zenodo: http://doi.org/10.5281/zenodo.3695300
  5. @MentoredSprints mentored-sprints.dev
 How it sprints work Choose project Pair up

    with someone Find an issue item to work on hands-on Get contributing 🎉 Check in with your mentor and let folks know you are working on it Projects intro soon Optional* https://bit.ly/mentoredsprints-22
  6. @MentoredSprints mentored-sprints.dev
 • Ask for help as needed • Be

    mindful and considerate • Struggling with an issue? They are the best to help with debugging and setup issues Notes about mentors https://mentored-sprints.netlify.app/participants/02-asking-questions/ https://bit.ly/mentoredsprints-22
  7. @MentoredSprints mentored-sprints.dev
 Finding a sprint buddy 󰟲 Someone interested in

    the same project 👀 An extra pair of eyes are helpful 󰢂 Ask first-some may not be comfortable with close contact/ interactions
  8. @MentoredSprints mentored-sprints.dev
 What makes a folder a “git repository”? 📁

    • Only one thing – the existence of a hidden .git directory. • Once this is present you can use the git status command https://bit.ly/mentoredsprints-22
  9. @MentoredSprints mentored-sprints.dev
 Forks 🍴 • Since you want to contribute

    back to the project we have to make a fork • A fork is your own copy of the source code that we will work on Repo_A - some GitHub account Repo_A_fork - your GitHub account https://bit.ly/mentoredsprints-22
  10. @MentoredSprints mentored-sprints.dev
 cloning 󰰁 • After making a fork you

    need to clone it locally Repo_A - some GitHub account Repo_A_fork - your GitHub account Your personal Computer (a.k.a local) Example: $ git clone https://github.com/scipy/scipy .git https://bit.ly/mentoredsprints-22
  11. @MentoredSprints mentored-sprints.dev
 working 󰟲 • You work on your fork

    Repo_A - some GitHub account Repo_A_fork - your GitHub account Your personal Computer (a.k.a local) Push to your Fork - i.e. add changes ✨ https://bit.ly/mentoredsprints-22
  12. @MentoredSprints mentored-sprints.dev
 This is how we ask the maintainers to

    incorporate our changes into the original repository PR (Pull request) 🎁 Repo_A - some GitHub account Repo_A_fork - your GitHub account https://bit.ly/mentoredsprints-22
  13. @MentoredSprints mentored-sprints.dev
 1. Find and issue or item to work

    on 2. Fork the repo and clone it locally 3. Make a new branch git branch new_branch 4. Change to new branch git switch new_branch 5. Work on changes 6. Run tests 7. Commit and push changes (sync your fork and clone) 8. Open a pr (from your remote fork) 9. Review and address comments 10. Celebrate when your PR is merged 🎉 PR lifecycle https://bit.ly/mentoredsprints-22
  14. @MentoredSprints mentored-sprints.dev
 You do not have to memorise this We

    have mentors here today! The best part https://bit.ly/mentoredsprints-22