[Numpy-discussion] "Become an Open Source Contributor" workshop

[Jaime Fernández del Río]

Apologies for the cross-posting.

The Data Science Student Society of the University of California San Diego,
or DS3 @ UCSD as they like to call themselves, will be holding biweekly
Python themed workshops starting this fall. On the week of October 19th,
they will be having yours truly doing a "Become an Open Source Contributor"
piece. It will be a shortish event, 60-90 minutes, so my idea was to cover
the following:

1. (15 min) An introduction to the Python data science landscape.
2. (30 min) An overview of the GitHub workflow that most (all?) of the
projects follow.
3. (30-45 min) A hands on session, where we would make sure everyone
gets set up in GitHub, and forks and clones their favorite project. Time
and participant willingness permitting, I would like to take advantage of
my commit bits, and have some of the participants submit a simple PR, e.g.
fixing a documentation typo, to NumPy or SciPy, and hit the green button
right there, so that they get to leave as knighted FOSS contributors.

And this is what I am hoping to get from you, the community:

1. If anyone in the area would like to get involved, please contact me.
I have recruited a couple of volunteers from PySanDiego, but could use more
help.
2. I'm also hoping to get some help, especially with the introductory
part. Given that the crowd will mostly be university students and some
faculty, it would be great if someone who actually knew what they were
talking about could deliver a short, 10 minute talk, on Python, data
science, and academia. I'm sure we could arrange it to have someone join
by video conference.
3. If you have organized anything similar in the past, and have material
that I could use to, ahem, draw inspiration from, or recommendations to
make, or whatever, I'd love to hear from you.

Thanks for reading!

Jaime

[Stefan van der Walt]

Hi Jaime

Post by Jaime Fernández del Río
3. If you have organized anything similar in the past, and have material
that I could use to, ahem, draw inspiration from, or recommendations to
make, or whatever, I'd love to hear from you.

Here's the new developer workflow page for scikit-image, I'm sure many
other projects have similar ones:

http://scikit-image.org/docs/stable/contribute.html

Perhaps you can harvest some ideas. Also, a beginner's summary to git
workflow:

http://rogerdudler.github.io/git-guide/

It's a lot to teach in only an hour or two, so if I were teaching I'd
keep it simple (basic) and clear (to make sure the students can "keep it
in their heads"), and to make sure they have a clear avenue for
questions when they get stuck after the class.

Stéfan

[Nathan Goldbaum]

If you are going to do work at a terminal, I'd suggest using a library like
doitlive (http://doitlive.readthedocs.org/en/latest/) so you can't make
mistakes while still making it look like you are actually typing everything
at a terminal. You will also be able to share your exact terminal sessions
with the students if they want to come back to it later.

Post by Stefan van der Walt
Hi Jaime

Post by Jaime Fernández del Río
3. If you have organized anything similar in the past, and have

material

Post by Jaime Fernández del Río
that I could use to, ahem, draw inspiration from, or recommendations

to

Post by Jaime Fernández del Río
make, or whatever, I'd love to hear from you.

Here's the new developer workflow page for scikit-image, I'm sure many
http://scikit-image.org/docs/stable/contribute.html
Perhaps you can harvest some ideas. Also, a beginner's summary to git
http://rogerdudler.github.io/git-guide/
It's a lot to teach in only an hour or two, so if I were teaching I'd
keep it simple (basic) and clear (to make sure the students can "keep it
in their heads"), and to make sure they have a clear avenue for
questions when they get stuck after the class.
Stéfan
_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

[Chris Barker]

Post by Nathan Goldbaum
If you are going to do work at a terminal, I'd suggest using a library
like doitlive (http://doitlive.readthedocs.org/en/latest/) so you can't
make mistakes while still making it look like you are actually typing
everything at a terminal.

This is pretty cool! And, I think perfect for a presentation or the like.

But for teaching, I find that one of the valuable things I do is make
mistakes at the command line (or iPython notebook, or editor...), and then
show the students how I discover and recover from the mistake...

just a thought....

-Chris

Post by Nathan Goldbaum
You will also be able to share your exact terminal sessions with the
students if they want to come back to it later.

Post by Stefan van der Walt
Hi Jaime

Post by Jaime Fernández del Río
3. If you have organized anything similar in the past, and have

material

Post by Jaime Fernández del Río
that I could use to, ahem, draw inspiration from, or recommendations

to

Post by Jaime Fernández del Río
make, or whatever, I'd love to hear from you.

Here's the new developer workflow page for scikit-image, I'm sure many
http://scikit-image.org/docs/stable/contribute.html
Perhaps you can harvest some ideas. Also, a beginner's summary to git
http://rogerdudler.github.io/git-guide/
It's a lot to teach in only an hour or two, so if I were teaching I'd
keep it simple (basic) and clear (to make sure the students can "keep it
in their heads"), and to make sure they have a clear avenue for
questions when they get stuck after the class.
Stéfan
_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

--
Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R [phone] voice
7600 Sand Point Way NE [phone] fax
Seattle, WA 98115 [phone] main reception

***@noaa.gov

[Charles R Harris]

On Wed, Sep 23, 2015 at 3:06 PM, Jaime Fernández del Río <

Post by Jaime Fernández del Río
Apologies for the cross-posting.
The Data Science Student Society of the University of California San
biweekly Python themed workshops starting this fall. On the week of
October 19th, they will be having yours truly doing a "Become an Open
Source Contributor" piece. It will be a shortish event, 60-90 minutes, so
1. (15 min) An introduction to the Python data science landscape.
2. (30 min) An overview of the GitHub workflow that most (all?) of the
projects follow.
3. (30-45 min) A hands on session, where we would make sure everyone
gets set up in GitHub, and forks and clones their favorite project. Time
and participant willingness permitting, I would like to take advantage of
my commit bits, and have some of the participants submit a simple PR, e.g.
fixing a documentation typo, to NumPy or SciPy, and hit the green button
right there, so that they get to leave as knighted FOSS contributors.

You could create a `foolscrap` repo in the numpy project on github and use
that. That would probably be useful for other people as well.

<snip>

Chuck

[Scott Collis]

Hey Jamie, List,
Having just come back from a conference where our toolkit, Py-ART [1]
has picked up a nice following of people keen to contribute I was
wondering if you will be opening this up via a google hangout or similar?

I would love to advertise this to our users. We all want more
contributors and a big roadblock is understanding the fork and pull
request system of GitHub

We did run a course that had some GitGub etc here:
https://github.com/scollis/SusSoPrac You are welcome to use anything
liberally!

Cheers,
Scott

Send NumPy-Discussion mailing list submissions to
To subscribe or unsubscribe via the World Wide Web, visit
https://mail.scipy.org/mailman/listinfo/numpy-discussion
or, via email, send a message with subject or body 'help' to
You can reach the person managing the list at
When replying, please edit your Subject line so it is more specific
than "Re: Contents of NumPy-Discussion digest..."
1. "Become an Open Source Contributor" workshop
(Jaime Fern?ndez del R?o)
2. Re: composition of the steering council (was Re: Governance
model request) (Travis Oliphant)
3. Re: Governance model request (Stefan van der Walt)
4. Re: Governance model request (Matthew Brett)
5. Re: composition of the steering council (was Re: Governance
model request) (Chris Barker)
----------------------------------------------------------------------
Message: 1
Date: Wed, 23 Sep 2015 14:06:08 -0700
Subject: [Numpy-discussion] "Become an Open Source Contributor"
workshop
Content-Type: text/plain; charset="utf-8"
Apologies for the cross-posting.
The Data Science Student Society of the University of California San Diego,
Python themed workshops starting this fall. On the week of October 19th,
they will be having yours truly doing a "Become an Open Source Contributor"
piece. It will be a shortish event, 60-90 minutes, so my idea was to cover
1. (15 min) An introduction to the Python data science landscape.
2. (30 min) An overview of the GitHub workflow that most (all?) of the
projects follow.
3. (30-45 min) A hands on session, where we would make sure everyone
gets set up in GitHub, and forks and clones their favorite project. Time
and participant willingness permitting, I would like to take advantage of
my commit bits, and have some of the participants submit a simple PR, e.g.
fixing a documentation typo, to NumPy or SciPy, and hit the green button
right there, so that they get to leave as knighted FOSS contributors.
1. If anyone in the area would like to get involved, please contact me.
I have recruited a couple of volunteers from PySanDiego, but could use more
help.
2. I'm also hoping to get some help, especially with the introductory
part. Given that the crowd will mostly be university students and some
faculty, it would be great if someone who actually knew what they were
talking about could deliver a short, 10 minute talk, on Python, data
science, and academia. I'm sure we could arrange it to have someone join
by video conference.
3. If you have organized anything similar in the past, and have material
that I could use to, ahem, draw inspiration from, or recommendations to
make, or whatever, I'd love to hear from you.
Thanks for reading!
Jaime