Name: Boris Bobrov
Contact/Email: bretonium or breton in IRC, firstname.lastname@example.org in jabber, <me AT bbreton DOT org>.
Background: I am a second-year student at Tashkent branch of Moscow State University, applied math and informatics faculty. I have 1.5 years of Python experience, 1 year of Django experience, finished a couple of local Django projects working for a local company, 11k LOC in one of them. I use git as my main vcs. Besides Python I know C (as good as Python), Bash (much worse than Python), C++ (current tasks in university are being written in it), js (2/3 of python knowledge, both "pure" and with jQuery) and LISP (Scheme) (basically helloworlds). Have good knowledge of HTML and CSS. Use Debian GNU/Linux as main OS. Have basic knowledge of system administration (set up nginx, uwsgi etc, familiar with cron, shell scripting). Familiar with unit tests and test-driven development techniques. Godlike when google is available.
Project title: Improving Debian Team Activity Metrics
Project details: SummerOfCode2012/Projects#Improving_Debian_Team_Activity_Metrics. I want to implement it in Python using Flask and SQLAlchemy. Files or sqlite3 will be used for caching, if needed (likely sqlite3, because it will allow to use existing Django ORM or SQLAlchemy). If it is impossible to use Flask or SQLAlchemy (because of current Debian infrastructure for example), Django will be used.
Synopsis: Implementation of Team Activity Metrics web interface with Python + one of the frameworks above.
Benefits to Debian: web interface for Team Activity Metrics with all necessary APIs and functions, for example "Select top N commiters", "Select top N talkers", "Select most active projects", "Show stats for the last X (days, months, years)" and others, as required by Team Metrics team.
Deliverables: Working web interface for Team Activity Metrics with required functions
Project schedule: It is pretty hard to tell what schedule it will be, because the details of all required functions and the data, which will be used, are not known. Though the skeleton of code with all required functions to connect and fetch data from db will be ready in 10 days after I start coding.
Exams and other commitments: I'll have exams from the 10 to 30 of June and will not be able to contribute a lot (though some code will still be written). 40-50% of the job I am planning to do in July/August.
Other summer plans: None, except maybe 2-4 days breaks when I will not be able to be online (but will still write the code).
Why Debian?: Firstly, I use Debian as my primary OS for about 3 years for now and I think it's a good way to contribute something back. Secondly, the task is solvable for me and I am pretty sure in succeeding in it. Thirdly, it is a great opportunity to get to know more about Debian and its infrastructure and a good way to join the community.
- I do apply to other projects.