Anonymous user
PyCon-2015-sprint-wiki: Difference between revisions
no edit summary
imported>Shauna (part one list of project requirements) |
imported>Shauna No edit summary |
||
Line 3:
__toc__
=== Project Name ===
* Django: No required technical knowledge or skills. Reading about the [https://docs.djangoproject.com/en/dev/internals/contributing](contribution process) would be useful. Ability to work independently is great. Cursory knowledge of git/pull requests would come in handy.▼
At this workshop?
List of useful skills:
People of all experience levels welcome:
Details about sprint tasks (if supplied):
==== To Sort ====
* OpenHatch:
▲* Django: No required technical knowledge or skills. Reading about the [https://docs.djangoproject.com/en/dev/internals/contributing
* Sage Math: Some mathematical knowledge and interest is highly useful.
* Stack Storm: General familiarity with linux / monitoring and other ""DevOps areas"" is required.
Line 15 ⟶ 28:
* Tryton: Python, XML format, Mercurial, Database (PostgreSQL or SQLite)
* PyLadies: No experience necessary. To work on project, will need python and virtualenv installed. We'll be working with: APIs, Data analytics & visualization (Python, IPython notebooks, Pandas, d3.js, etc), Python-based websites (e.g. Flask, Django), Front-end knowledge (CSS, JS, HTML), Documentation (rST markup, Sphinx, read the docs)
* Hey Duwamish!: Please be familiar with git and unix command line basics. I am happy to provide training on just about anything else, from MVC basics to front-end design and database models.
* Kinect: Hope people know Python and are excited about using Kinect in their projects/experiments.
* Quantifec Code: "They should only be familiar with Python and be passionate about code quality!"
** At QuantifiedCode we try to build the best Python code checker in the galaxy, so we want to discuss with people how we can help them to write better code and make them more productive. So what we propose is a ""Python anti-pattern"" sprint, where people can talk about best practices and anti-patterns that they encounter in their work and we will try to automate the detection of these patterns in their projects. Like this, open-source projects will have a way to provide new contributers with coding guidelines tailored to their needs and conventions, and thus make it much easier for people to contribute good, readable and correct code to their projects.
* CPython: Some C or Python or both.
* "Python beginners and educators are welcome to provide input on how to make IDLE a better educational tool for beginners.
** In prep for these IDLE changes, I'd like to make a demo app on tkinter widgets (similar to wxPython's Demo app) and how to work with the tkinter module. Those with tkinter experience are very welcome."
* Mochi: Language design, testing, documentation, functional programming
* JyNI: "Participating is only feasible for people that can already at least roughly read C-code. Experience in C programming is recommended, but there are also refactoring and code-arrangement and cleanup-tasks that can be done by moving existing code around; that's why reading C-code is already enough for some tasks. In addition to improving C-skills I provide guidance for and insight into Python's C-extension API and also into Jython, how to use it, how it works."
| |||