Differences between revisions 3 and 9 (spanning 6 versions)
Revision 3 as of 2015-03-04 00:26:35
Size: 1297
Editor: berkerpeksag
Comment: Update Python core dev channel name adn mention about freenode
Revision 9 as of 2015-03-24 10:39:07
Size: 4768
Editor: EzioMelotti
Comment: Add a couple of links.
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
= No ideas here yet! = = Ideas =
Line 16: Line 16:

== 1. bugs.python.org improvements ==

 * '''Project description''': The goal of this project is to improve the [[https://bugs.python.org/|bug tracker used by CPython]].
 * '''Skills''': Python, HTML/CSS/JS, Roundup, DVCS.
 * '''Difficulty level''': Intermediate.
 * '''Related Readings/Links''': The details are still being discussed on the [[https://mail.python.org/pipermail/core-workflow/2015-March/thread.html#132|core-workflow ML]].
 * '''Potential mentors''': Ezio Melotti.

=== Project Details ===

There are several different tasks that can be tackled.

 * Some features previously discussed on this ML and summarized at https://wiki.python.org/moin/TrackerDevelopmentPlanning
 * Some other miscellaneous features listed at https://wiki.python.org/moin/DesiredTrackerFeatures
 * Better integration with Rietveld (e.g. add messages to roundup when someone posts a review)
 * Smarter branch detection in patches (sometimes patches don't get the review link)
 * Patch analysis (information such as affected files could be extracted from the files and used by Roundup, check pep8 compliance)
 * Integration with BitBucket (and possibly GitHub) pull requests (might use https://pypi.python.org/pypi/vcs)
 * Investigate Kallithea/Phabricator integration
 * Mercurial extension to simplify tracker interaction (e.g. upload patches automatically, might be based on https://bitbucket.org/ncoghlan/cpydev/src/default/cpyhg.py?at=default - might be similar to https://github.com/openstack-infra/git-review)
 * Reviewing and applying patches submitted on the meta-tracker
 * Fix other issues listed on the meta-tracker

Students can select a substantial subset of these tasks for their proposal.
The actual tasks and the order can be discussed with the mentor.


== 2. Add a REST API to Roundup ==

 * '''Project description''': The goal of this project is to add a REST API to Roundup
 * '''Skills''': Python, basic HTML/JS skills.
 * '''Difficulty level''': Intermediate.
 * '''Related Readings/Links''': http://issues.roundup-tracker.org/issue2550734 http://sourceforge.net/p/roundup/mailman/message/33589328/
 * '''Potential mentors''': Hieu Nguyen.

=== Project Details ===

For this project the student will design and develop a REST API for bugs.python.org.
Even though this project is initially aimed to bugs.python.org, the plan is to eventually contribute the code upstream.
This is what the student is expect to do during the project:

 1. design the REST API (see also https://mail.python.org/pipermail/core-workflow/2015-March/000142.html)
 2. implement it in our Roundup clone (https://hg.python.org/tracker/roundup/)
 3. develop some basic tool that uses the API (improved stats page, [[https://dashboard.djangoproject.com/|dashboard]])
 4. possibly tweak the API if there are problems
 5. when stable, contribute it upstream (could happen after GSoC)

== 3. Use more unittest features in regrtest ==

 * '''Project description''': The goal of this project is to improve the CPython test suite by using more unittest features.
 * '''Skills''': Python, unittest.
 * '''Difficulty level''': Intermediate.
 * '''Related Readings/Links''': http://bugs.python.org/issue10967, https://hg.python.org/cpython/file/default/Lib/test/regrtest.py
 * '''Potential mentors''': No mentor (you can put together a proposal and ask for one on [[https://mail.python.org/mailman/listinfo/core-mentorship|the core mentorship ML]]).

CPython

CPython is the default, most widely used implementation of the Python programming language. It is mostly written in C, most of the modules are written in Python itself. In case you want to make the changes which will be used by all the Python programmers worldwide, this is the project to work for.

Contacting CPython developers

One can contact the core developers over IRC or using mailing lists. #python-dev (on freenode) is the channel for core developers, the core mentorship mailing list is the place to an email discussion. Remember that the developers are may not be in your timezone, so it might take time to get a reply from anyone.

Getting Started

The best place to get started is the devguide. You will find all the instructions required to build your own CPython. Before contacting the mentors, it is better you start solving few bugs first.

Ideas

We're still waiting to find out which mentors are available for Core Python/CPython projects. In the meantime, you can discuss ideas on the core mentorship mailing list.

1. bugs.python.org improvements

  • Project description: The goal of this project is to improve the bug tracker used by CPython.

  • Skills: Python, HTML/CSS/JS, Roundup, DVCS.

  • Difficulty level: Intermediate.

  • Related Readings/Links: The details are still being discussed on the core-workflow ML.

  • Potential mentors: Ezio Melotti.

Project Details

There are several different tasks that can be tackled.

Students can select a substantial subset of these tasks for their proposal. The actual tasks and the order can be discussed with the mentor.

2. Add a REST API to Roundup

Project Details

For this project the student will design and develop a REST API for bugs.python.org. Even though this project is initially aimed to bugs.python.org, the plan is to eventually contribute the code upstream. This is what the student is expect to do during the project:

  1. design the REST API (see also https://mail.python.org/pipermail/core-workflow/2015-March/000142.html)

  2. implement it in our Roundup clone (https://hg.python.org/tracker/roundup/)

  3. develop some basic tool that uses the API (improved stats page, dashboard)

  4. possibly tweak the API if there are problems
  5. when stable, contribute it upstream (could happen after GSoC)

3. Use more unittest features in regrtest

SummerOfCode/2015/python-core (last edited 2015-03-24 10:39:07 by EzioMelotti)

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