Feedback from sprint (make updates for next year's sprint)

[reshamas]

1. add how to find issues to work on
2. guide for how to pair program

[amueller]

also how to do the second pr: go back to master before making a new branch

[reshamas]

Sprint report has list of suggestions. They are included here.

https://reshamas.github.io/data-umbrella-scikit-learn-online-sprint-report/

Adjustments for Next Sprint

Application Form: reminder for spam

Remind participants that communication is sent from other platforms (Mailchimp, Eventbrite, etc) and it may go to spam. It would be good to keep an eye out on the spam folder or email the sprint organizer if they have not heard back.

Application Form: pronouns

Ask for preferred pronoun on application and also to include on website for contributors.

Issues

Add in a slide to explain to participants how to look for issues to work on.

Pair Programming

Add in a slide explaining how pair programming works.

Second Pull Request

Update slides / documentation to show how to submit a second PR.

Pair Partner

Explore how to optimally match participants as pair partners based on experience.

Platforms

Three platforms (Zoom, Discord and Gitter) were confusing for attendees. One platform was preferred.

Scikit-learn Mailing List

Include link to scikit-learn mailing list in communications. Encourage participants to sign up for the mailing list to keep up to date on discussions. The mailing list is also a good way to learn about open source, the library and the community.
https://mail.python.org/mailman/listinfo/scikit-learn

Setting up virtual environment

We encouraged people to set up their virtual environment beforehand. The dilemna here is if we make it optional, more people probably would not do it. If we make it required, people who do not set up beforehand may not attend the sprint. Some people had difficulty setting up their environment and thought they could only join the sprint if their set up was ready. Action: find a way to optimize set up before the sprint while providing support for those who need it.

[reshamas]

Application:  collect info in separate fields

• First Name
• Last Name
• City
• State
• Country

[reshamas]

Go through folder structure of scikit-learn repo and explain the folders and files (tests, etc).

[reshamas]

We encourage people to begin with documentation changes. Can we provide some direction on when they should do code changes?
Can go through issues list as well and go over tags in video or presentation.