Hackathon
Version 1 (Vadim Pisarevsky, 2013-01-24 07:27 pm)
| 1 | 1 | h1. Hackathon |
|
|---|---|---|---|
| 2 | 1 | ||
| 3 | 1 | _+hackathon=hack+marathon+_ |
|
| 4 | 1 | ||
| 5 | 1 | A hackathon is an event in which computer programmers and others in the field of software development collaborate intensively on software-related projects. |
|
| 6 | 1 | ||
| 7 | 1 | h3. The Purpose |
|
| 8 | 1 | ||
| 9 | 1 | For this hackathon, our goal is increasing code stability to make the library steady as possible. |
|
| 10 | 1 | ||
| 11 | 1 | * Improve library stability |
|
| 12 | 1 | * Provide feedback to our customers |
|
| 13 | 1 | ||
| 14 | 1 | h3. Organization |
|
| 15 | 1 | ||
| 16 | 1 | Hackathon duration is one week (from 26 March to 30 March). You should try to be in the office from 11 a.m. to 6 p.m. All communication activities will be at this time. |
|
| 17 | 1 | ||
| 18 | 1 | Each developer get own area of ââresponsibility: |
|
| 19 | 1 | ||
| 20 | 1 | |Maria | mll, features2d| |
|
| 21 | 1 | |Alex R., Andrey M. | FFMPEG, highgui | |
|
| 22 | 1 | |Ilya | calib3d| |
|
| 23 | 1 | |Alex Sh. | build/install, tests, compilation| |
|
| 24 | 1 | |Vadim | patches| |
|
| 25 | 1 | |Vlad and Alexey| GPU module| |
|
| 26 | 1 | |Ivan and Marina || |
|
| 27 | 1 | ||
| 28 | 1 | Issues priorities in descending order: |
|
| 29 | 1 | * bug with provided solution (Patch with High priority) |
|
| 30 | 1 | * bug (from High to Low priorities) |
|
| 31 | 1 | * patch |
|
| 32 | 1 | * feature |
|
| 33 | 1 | ||
| 34 | 1 | h3. Hacker Guide |
|
| 35 | 1 | ||
| 36 | 1 | You should right a test before the bug fix. This is very important to see your test failing, because later it will control regressions. Then, if you see it failing, you can fix the bug. This idea is very close to TDD's "Reg-Green-Refactor":http://blog.goyello.com/2011/09/13/red-green-refactor-cycle/ mantra. |
|
| 37 | 1 | ||
| 38 | 1 | Preferred sequence of actions: |
|
| 39 | 1 | * assign issue. You should choose more prioritet issue from the list of "hackathon issues":http://code.opencv.org/projects/opencv/issues?query_id=15 |
|
| 40 | 1 | * add test. This means that you have to have a failing test first. You canât write any production code before âredâ. |
|
| 41 | 1 | * fix problem. When you have compiling but failing test you can write some production code to satisfy the test |
|
| 42 | 1 | * commit changes to the repository. In commit message you should use #$$$$ template to link it with the issue. |
|
| 43 | 1 | * change issue status to _Done_. You should use r$$$$ template in issue updating. |
|
| 44 | 1 | ||
| 45 | 1 | If in doubt, please, assign task to alexander.shishkov before or after commit. |
|
| 46 | 1 | ||
| 47 | 1 | If you want to discuss something with all Hackathon participants, please, use "forum":http://code.opencv.org/projects/opencv/boards. |
|
| 48 | 1 | ||
| 49 | 1 | ||
| 50 | 1 | ||
| 51 | 1 | h3. Links |
|
| 52 | 1 | ||
| 53 | 1 | * "OpenCV hackathon slides":https://docs.google.com/a/itseez.com/presentation/d/1IvUOXAJ7FYO2NhplYTGJ0MvTjzKhJnSRano22yuaho4/edit#slide=id.gae260d7_1_17 |
|
| 54 | 1 | * "About hackathon":http://en.wikipedia.org/wiki/Hackathon |