Differences between revisions 39 and 40
Revision 39 as of 2015-03-06 17:33:19
Size: 18861
Editor: TerriOda
Comment: Adding scrapinghub
Revision 40 as of 2015-03-07 01:29:33
Size: 18905
Editor: JuliaMedina
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
Line 5: Line 4:
The 2015 PSF GSoC coordinator is TerriOda. (terri on Freenode IRC, terrioda at gmail.com)  The 2015 PSF GSoC coordinator is TerriOda. (terri on Freenode IRC, terrioda at gmail.com)
Line 7: Line 6:
The other org admins include James Lopeman (meflin on IRC) and Florian Fuchs (florianf on IRC), and Kushal Das (kushal on IRC).  The other org admins include James Lopeman (meflin on IRC) and Florian Fuchs (florianf on IRC), and Kushal Das (kushal on IRC).
Line 14: Line 13:
Line 16: Line 14:
  * The [[http://en.flossmanuals.net/GSoCStudentGuide/|GSoC Student Guide]], which includes a lot of really useful information and tips for prospective GSoC students, including a page on [[http://en.flossmanuals.net/GSoCStudentGuide/ch006_making-first-contact/|making first contact with prospective mentors]].
   * The Python GSoC FAQ: SummerOfCode/FrequentlyAskedQuestions
  * The [[http://en.flossmanuals.net/GSoCStudentGuide/|GSoC Student Guide]], which includes a lot of really useful information and tips for prospective GSoC students, including a page on [[http://en.flossmanuals.net/GSoCStudentGuide/ch006_making-first-contact/|making first contact with prospective mentors]].
  * The Python GSoC FAQ: SummerOfCode/FrequentlyAskedQuestions
Line 19: Line 17:
   * This mailing list is open to students, mentors and other interested community members
   * This is your first place to ask questions related to summer of code with Python!
 * IRC: '''#python-gsoc on irc.freenode.net'''.  
   * If you don't have an IRC client set up, you can [[http://webchat.freenode.net/?nick=gsoc_....&channels=python-gsoc|use this link to open a web chat client]] 
 * Org admins: 
   * 99.9% of the time, students should email soc2015-general@python.org with questions (it reaches more people so you get an answer faster)
    * Mentors and sub-org admins can email Terri, Meflin and Florian all at once using the mail alias soc2015-general-owner(at)python.org to get more information about the program and get signed up.
  * This mailing list is open to students, mentors and other interested community members
  * This is your first place to ask questions related to summer of code with Python!
 * IRC: '''#python-gsoc on irc.freenode.net'''.
  * If you don't have an IRC client set up, you can [[http://webchat.freenode.net/?nick=gsoc_....&channels=python-gsoc|use this link to open a web chat client]]
 * Org admins:
  * 99.9% of the time, students should email soc2015-general@python.org with questions (it reaches more people so you get an answer faster)
  * Mentors and sub-org admins can email Terri, Meflin and Florian all at once using the mail alias soc2015-general-owner(at)python.org to get more information about the program and get signed up.
Line 30: Line 28:
Line 37: Line 34:
 2. '''Start communicating with the developers.''' Join the mailing list, IRC channel, or any other communication channels the developers use. Listen, get to know the people involved, and ask questions.
  * If you want to make the best first impression, DO NOT start emails with "Dear Sir." Python has many mentors who are female and/or prefer other forms of address. Try "Dear developers" or "Dear mentors" if you're sending a general email, or use whatever name they use on their email if you're addressing a specific person. Culturally speaking, first names or chosen nicknames are fine for most open source projects. 
 3. '''Set up your own development environment.'''
 4. '''Find some beginner-friendly bugs and try to fix them.''' Many projects have these tagged as "easy" "bite-size" or "beginner-friendly"
 1. '''Start communicating with the developers.''' Join the mailing list, IRC channel, or any other communication channels the developers use. Listen, get to know the people involved, and ask questions.
  * If you want to make the best first impression, DO NOT start emails with "Dear Sir." Python has many mentors who are female and/or prefer other forms of address. Try "Dear developers" or "Dear mentors" if you're sending a general email, or use whatever name they use on their email if you're addressing a specific person. Culturally speaking, first names or chosen nicknames are fine for most open source projects.
 1. '''Set up your own development environment.'''
 1. '''Find some beginner-friendly bugs and try to fix them.''' Many projects have these tagged as "easy" "bite-size" or "beginner-friendly"
Line 44: Line 41:
 5. '''Find bugs and report them.''' Hopefully you won't encounter too many, but it's always a good idea to get familiar with your project's bug reporting process.
 6. '''Help with documentation.''' As a beginner in your project, you're going to see things that are confusing that more experienced developers may not notice. Take advantage of your beginner mindset and make sure to document anything you think is missing!
 7. '''Help others.''' This is a great idea for a lot of reasons: explaining things can help you learn them better, demonstrating your skills as a good community member can make you more memorable when your mentors have to choose candidates, and being helpful makes your community a better place!
 1. '''Find bugs and report them.''' Hopefully you won't encounter too many, but it's always a good idea to get familiar with your project's bug reporting process.
 1. '''Help with documentation.''' As a beginner in your project, you're going to see things that are confusing that more experienced developers may not notice. Take advantage of your beginner mindset and make sure to document anything you think is missing!
 1. '''Help others.''' This is a great idea for a lot of reasons: explaining things can help you learn them better, demonstrating your skills as a good community member can make you more memorable when your mentors have to choose candidates, and being helpful makes your community a better place!
Line 55: Line 52:
Line 57: Line 53:
Interested in mentoring?   Interested in mentoring?
Line 61: Line 57:
To get signed up as an offical mentor, contact your sub-org admin.   To get signed up as an offical mentor, contact your sub-org admin.
Line 66: Line 62:
Line 70: Line 65:
Line 71: Line 67:
 2. You need at least 3 mentors (a sub-org admin plus 2 more) signed up for the whole summer.
 3. You need to have a good ideas page available online. (Including well-described project ideas that can be completed during the GSoC period, as well as lots of "how to get started" information. See SummerOfCode/OrgIdeasPageTemplate for a starting template.) 
 1. You need at least 3 mentors (a sub-org admin plus 2 more) signed up for the whole summer.
 1. You need to have a good ideas page available online. (Including well-described project ideas that can be completed during the GSoC period, as well as lots of "how to get started" information. See SummerOfCode/OrgIdeasPageTemplate for a starting template.)
Line 79: Line 75:
Line 83: Line 78:


||<style="text-align:center" |3> {{http://nipy.org/dipy/_static/dipy-banner.png||width=240}} ||<style="color:#366D9C;font-size:140%;font-weight:bold;">Dipy ||
||<style="text-align:center" |3> {{http://nipy.org/dipy/_static/dipy-banner.png||width="240"}} ||<style="color:#366D9C;font-size:140%;font-weight:bold;">Dipy ||
Line 87: Line 80:
||<style="text-align:center">[[http://nipy.org/dipy/|Website]] | [[ http://mail.scipy.org/mailman/listinfo/nipy-devel|Mailing list]] |[[https://github.com/nipy/dipy/wiki/Google-Summer-of-Code-2015|Ideas Page]] || ||<style="text-align:center">[[http://nipy.org/dipy/|Website]] | [[http://mail.scipy.org/mailman/listinfo/nipy-devel|Mailing list]] |[[https://github.com/nipy/dipy/wiki/Google-Summer-of-Code-2015|Ideas Page]] ||
Line 91: Line 84:
||<style="text-align:center" |3> {{http://martinos.org/mne/stable/_static/mne_logo.png||width=240}} ||<style="color:#366D9C;font-size:140%;font-weight:bold;">MNE-Python || ||<style="text-align:center" |3> {{http://martinos.org/mne/stable/_static/mne_logo.png||width="240"}} ||<style="color:#366D9C;font-size:140%;font-weight:bold;">MNE-Python ||
Line 96: Line 89:
||<style="text-align:center">[[https://moinmo.in/|Wiki]] | [[https://moinmo.in/MoinMoinMailingLists|Mailing List]] | [[https://moinmo.in/GoogleSoc2015/InitialProjectIdeas|Ideas Page]] | [[https://moinmo.in/GoogleSoc2015|MoinMoin GSoC main page]]||
||<style="text-align:center" |3> NetworkX ||<style="color:#366D9C;font-size:140%;font-weight:bold;">NetworkX ||
||NetworkX is a software package for the creation, manipulation, and study of the structure, dynamics, and function of complex networks.||
||<style="text-align:center">[[https://networkx.github.io/|Home Page]] | [[https://groups.google.com/forum/#!forum/networkx-discuss|Mailing List]] | [[https://github.com/networkx/networkx/wiki/GSoC-2015|Ideas Page]]||
||<style="text-align:center" |3> {{http://pgmpy.org/_images/logo.png||width=240}} ||<style="color:#366D9C;font-size:140%;font-weight:bold;">pgmpy ||
||<style="text-align:center">[[https://moinmo.in/|Wiki]] | [[https://moinmo.in/MoinMoinMailingLists|Mailing List]] | [[https://moinmo.in/GoogleSoc2015/InitialProjectIdeas|Ideas Page]] | [[https://moinmo.in/GoogleSoc2015|MoinMoin GSoC main page]] ||
||<style="text-align:center" |3>NetworkX ||<style="color:#366D9C;font-size:140%;font-weight:bold;">NetworkX ||
||NetworkX is a software package for the creation, manipulation, and study of the structure, dynamics, and function of complex networks. ||
||<style="text-align:center">[[https://networkx.github.io/|Home Page]] | [[https://groups.google.com/forum/#!forum/networkx-discuss|Mailing List]] | [[https://github.com/networkx/networkx/wiki/GSoC-2015|Ideas Page]] ||
||<style="text-align:center" |3> {{http://pgmpy.org/_images/logo.png||width="240"}} ||<style="color:#366D9C;font-size:140%;font-weight:bold;">pgmpy ||
Line 103: Line 96:
||<style="text-align:center" |3> {{https://cloud.githubusercontent.com/assets/276007/6099565/a4268f1e-afb0-11e4-8cd4-e6a8eb398288.png||width=200}} ||<style="color:#366D9C;font-size:140%;font-weight:bold;">PyDy ||
|| Multibody Dynamics with Python ||
||<style="text-align:center" |3> {{https://cloud.githubusercontent.com/assets/276007/6099565/a4268f1e-afb0-11e4-8cd4-e6a8eb398288.png||width="200"}} ||<style="color:#366D9C;font-size:140%;font-weight:bold;">PyDy ||
||Multibody Dynamics with Python ||
Line 106: Line 99:
||<style="text-align:center" |3> {{http://scikit-image.org/_static/img/logo.png||width=240}} ||<style="color:#366D9C;font-size:140%;font-weight:bold;">scikit-image || ||<style="text-align:center" |3> {{http://scikit-image.org/_static/img/logo.png||width="240"}} ||<style="color:#366D9C;font-size:140%;font-weight:bold;">scikit-image ||
Line 112: Line 105:
||<style="text-align:center" |3> {{https://s3.amazonaws.com/uploads.hipchat.com/19745/1178307/k7gAK1gzIfqsyKR/shub-logo.jpg||width=240}} ||<style="color:#366D9C;font-size:140%;font-weight:bold;">Scrapinghub || ||<style="text-align:center" |3> {{https://s3.amazonaws.com/uploads.hipchat.com/19745/1178307/k7gAK1gzIfqsyKR/shub-logo.jpg||width="240"}} ||<style="color:#366D9C;font-size:140%;font-weight:bold;">Scrapinghub ||
Line 114: Line 107:
||<style="text-align:center">[[http://scrapinghub.com/|Website]] | [[http://gsoc2015.scrapinghub.com/|Ideas Page]] ||
||<style="text-align:center" |3> {{http://www.sympy.org/media/logo.png||width=240}} ||<style="color:#366D9C;font-size:140%;font-weight:bold;">SymPy ||
|| Symbolic mathematics (computer algebra system) ||
||<style="text-align:center">[[http://scrapinghub.com/|Website]] | [[http://gsoc2015.scrapinghub.com/participate/|Mailing Lists]] | [[http://gsoc2015.scrapinghub.com/|Ideas Page]] ||
||<style="text-align:center" |3> {{http://www.sympy.org/media/logo.png||width="240"}} ||<style="color:#366D9C;font-size:140%;font-weight:bold;">SymPy ||
||Symbolic mathematics (computer algebra system) ||
Line 121: Line 114:
||<style="text-align:center" |3> {{http://vispy.org/_static/img/logo.png||width=240}} ||<style="color:#366D9C;font-size:140%;font-weight:bold;">Vispy || ||<style="text-align:center" |3> {{http://vispy.org/_static/img/logo.png||width="240"}} ||<style="color:#366D9C;font-size:140%;font-weight:bold;">Vispy ||
Line 125: Line 118:


Line 126: Line 122:
Line 128: Line 123:
Line 136: Line 130:


Line 137: Line 134:
Line 141: Line 137:
Line 157: Line 154:
Line 159: Line 155:
 * The main GSoC website is [[http://www.google-melange.com/gsoc/homepage/google/gsoc2015]].  * The main GSoC website is http://www.google-melange.com/gsoc/homepage/google/gsoc2015.

Google Summer of Code 2015 @ the Python Software Foundation

Google Summer of Code is a global program that offers post-secondary students an opportunity to be paid for contributing to an open source project over a three month period. Since 2005, the Python Software Foundation has served as as an "umbrella organization" to a variety of python-related projects, as well as sponsoring projects related to the development of the Python language. It is our intention to apply as a mentoring organization again in 2015, and this page coordinates those efforts.

The 2015 PSF GSoC coordinator is TerriOda. (terri on Freenode IRC, terrioda at gmail.com)

The other org admins include James Lopeman (meflin on IRC) and Florian Fuchs (florianf on IRC), and Kushal Das (kushal on IRC).

More org admins may be announced later. If you're interested in volunteering, contact Terri.

Mailing lists, IRC, and other ways to get in touch

Please note that Python has a Community Code of Conduct and mentors and students working with the PSF are asked to abide by it as members of the Python community.

Preparing for GSoC 2015

Please note the Dates and deadlines for 2015. We won't know if Python is a GSoC 2015 mentoring org until March 2nd. You can expect a reasonable number of GSoC ideas linked from this page by February 20th (the org application deadline), and list of Python sub-orgs around March 17th.

Students

Here's 7 steps to help you get started:

  1. Choose an organization to work with. Python has a lot of sub-projects (over 20 in 2014!), so this can be hard. See "How do I choose a project or a sub-org?" if you need help. You can try out the next steps with more than one org and make your decision once you get to know them, too!

  2. Start communicating with the developers. Join the mailing list, IRC channel, or any other communication channels the developers use. Listen, get to know the people involved, and ask questions.

    • If you want to make the best first impression, DO NOT start emails with "Dear Sir." Python has many mentors who are female and/or prefer other forms of address. Try "Dear developers" or "Dear mentors" if you're sending a general email, or use whatever name they use on their email if you're addressing a specific person. Culturally speaking, first names or chosen nicknames are fine for most open source projects.
  3. Set up your own development environment.

  4. Find some beginner-friendly bugs and try to fix them. Many projects have these tagged as "easy" "bite-size" or "beginner-friendly"

    • Note that if you apply as a student with the PSF you will be asked to submit a code sample, generally code related to your project. A few fixed bugs with code accepted upstream will make your application look great!
    • Having trouble figuring out which bugs are beginner-friendly? Send an email to the project mailing list saying something like "Hi, I'm a student developer interested in getting some open source experience and I was wondering if anyone could suggest some bugs that are suitable for a beginner in this project?"
    • Some projects have beginner-friendly "bite-sized" bugs listed in the OpenHatch search engine, found here: http://openhatch.org/search/

  5. Find bugs and report them. Hopefully you won't encounter too many, but it's always a good idea to get familiar with your project's bug reporting process.

  6. Help with documentation. As a beginner in your project, you're going to see things that are confusing that more experienced developers may not notice. Take advantage of your beginner mindset and make sure to document anything you think is missing!

  7. Help others. This is a great idea for a lot of reasons: explaining things can help you learn them better, demonstrating your skills as a good community member can make you more memorable when your mentors have to choose candidates, and being helpful makes your community a better place!

Not sure which projects will be participating in 2015? Well, neither are we! Many orgs won't decide until they can get commitment from mentors, and often mentors don't know their schedules until closer to the start of the GSoC period. But you can take a look at the list of organizations who participated in 2014 or previous years to get an idea of what projects might be participating. If you're interested in a Python-based project that hasn't participated in GSoC in the past, feel free to tell them to get in touch with Terri and the other org admins to learn more about participating in 2015. They can reach all the org admins at the following email alias: soc2015-general-owner(at)python.org

More information about writing your application will be available here closer to the start of the student application period.

Mentors

Interested in mentoring?

The GSoC Mentors guide can tell you a whole lot about what the job entails. This is based on information compiled from many experienced mentors!

To get signed up as an offical mentor, contact your sub-org admin.

If you're not involved with any sub-org participating in GSoC but would still like to volunteer, get in touch with the Python org admins at soc2015-general-owner(at)python.org. There are often projects looking for more mentors and we'd be happy to get you in touch with someone who needs help!

New Sub-orgs

If you're a python-based project who'd like to participate in GSoC but hasn't done this before...

In short, we ask for 3 things:

  1. Your project needs to be a reasonably established python project.
  2. You need at least 3 mentors (a sub-org admin plus 2 more) signed up for the whole summer.
  3. You need to have a good ideas page available online. (Including well-described project ideas that can be completed during the GSoC period, as well as lots of "how to get started" information. See SummerOfCode/OrgIdeasPageTemplate for a starting template.)

Please get in touch with TerriOda and Python org admins at soc2015-general-owner(at)python.org.to learn more about what we need from you, what you can expect from us, and how to get involved.

Alas, we don't have the resources to accept every project, but we try to support projects with a clear commitment to python!

Python Project Ideas

Ideas for projects and links to Python-related teams' idea pages will appear here once mentors have gotten in touch with TerriOda. (You can also check last year's page to find projects that might participate again.) We expect the 2015 page to be complete around March 7th. (Why March 7th? Google makes their decisions about mentoring orgs on March 2nd, and usually some of the ones who were too small will join us after that date.)

If you are unsure if your favourite Python project will be participating, ask them and encourage them to sign up!

http://nipy.org/dipy/_static/dipy-banner.png

Dipy

Dipy is a free and open source software project focusing mainly on diffusion magnetic resonance imaging (dMRI) analysis.

Website | Mailing list |Ideas Page

Kivy Logo

Kivy Organization

Kivy is a cross-platform Python toolkit for the rapid development of applications that make use of innovative user interfaces, such as multi-touch apps.

Website | #kivy on Freenode | wiki |kivy-users Google Group | GSOC Ideas Page

http://martinos.org/mne/stable/_static/mne_logo.png

MNE-Python

MNE is a software package for processing magnetoencephalography (MEG) and electroencephalography (EEG) data.

Website | Mail List | Ideas Page

https://moinmo.in/moin_static19/common/moinmoin.png

MoinMoin Wiki

MoinMoin Wiki is a popular wiki engine in Python. It runs THIS site.

Wiki | Mailing List | Ideas Page | MoinMoin GSoC main page

NetworkX

NetworkX

NetworkX is a software package for the creation, manipulation, and study of the structure, dynamics, and function of complex networks.

Home Page | Mailing List | Ideas Page

http://pgmpy.org/_images/logo.png

pgmpy

Python library for Probabilistic Graphical Models

Website | Mailing List | #pgmpy on Freenode | Ideas Page

https://cloud.githubusercontent.com/assets/276007/6099565/a4268f1e-afb0-11e4-8cd4-e6a8eb398288.png

PyDy

Multibody Dynamics with Python

Website | pydy@googlegroups.com | Ideas page | Chat (Gitter)

http://scikit-image.org/_static/img/logo.png

scikit-image

scikit-image is an image processing package for the SciPy ecosystem

Website | Mailing List | IRC|Ideas Page

http://www.scipy.org/_static/images/scipy_med.png

SciPy/NumPy

SciPy (pronounced "Sigh Pie") is open-source software for mathematics, science, and engineering. The SciPy library depends on NumPy, which provides convenient and fast N-dimensional array manipulation.

Website | Mailing Lists | Ideas Page

https://s3.amazonaws.com/uploads.hipchat.com/19745/1178307/k7gAK1gzIfqsyKR/shub-logo.jpg

Scrapinghub

Scrapinghub is a company focused on information retrieval and its later manipulation, deeply involved on developing and contributing in Open Source projects regarding web crawling and data processing technologies. This year we are applying with three of our most renowned projects, Scrapy, Portia and Splash.

Website | Mailing Lists | Ideas Page

http://www.sympy.org/media/logo.png

SymPy

Symbolic mathematics (computer algebra system)

Website | sympy@googlegroups.com | Ideas page | Chat (Gitter)

http://deeplearning.net/software/theano/_static/theano_logo_allblue_200x46.png

Theano

Theano is an optimizing compiler for numpy.ndarray and scipy.sparse matrix that generate GPU code and do symbolic differentiation

Website | theano-dev@googlegroups.com |Ideas Page

http://vispy.org/_static/img/logo.png

Vispy

High-performance interactive visualization in Python

Website | vispy@googlegroups.com | Ideas page

Friends of the PSF

These organizations applied and got in to Google Summer of Code separately, but we've worked with them in the past and they're awesome! If you wish to work with one of these groups, you should apply to them directly.

http://farm8.staticflickr.com/7432/12526610733_5a83e0b5f7_o.png

GNU Mailman

Mailing list package written in Python

Website | mailman-developers@python.org | #mailman on Freenode | Ideas Page

http://www.astro.utoronto.ca/~kerzendorf/files/larger_logo_smaller.png

TARDIS-SN

Supernova radiative transfer in Python

Website | tardis-sn-dev@googlegroups.com | Ideas Page

Dates/Deadlines

Google's dates and deadlines for 2015.

Of note:

  • Feb 20: Mentoring organization application deadline. (There should be a decent number of ideas on this page by then.)
  • Mar 16: Deadline for new organizations wanting to be under the Python umbrella to have their mentors and ideas pages ready (Please contact TerriOda.) **

  • Mar 27: Student application deadline.
  • Apr 18: Python sub-orgs need to get their student picks to TerriOda **

  • Apr 27: Accepted student proposals announced on the Google Summer of Code 2015 site.
  • May 25: Students begin coding.
  • Jul 1: Midterm evaluations due to Python **
  • Jul 3: Midterms evaluations due to Google
  • Aug 26: Final evaluations due to Python **
  • Aug 28: Final evaluations due to Google

** These are Python-specific deadlines for mentors and sub-org admins. They're typically a few days before Google's official deadlines to allow Terri enough time to deal with any problems that might occur.

The time for all these deadlines is 1900UTC. See what time that is in other time zones.

More Information

SummerOfCode/2015 (last edited 2016-02-02 16:17:32 by EzioMelotti)

Unable to edit the page? See the FrontPage for instructions.