Hackathon¶

hackathon=hack+marathon

A hackathon is an event in which computer programmers and others in the field of software development collaborate intensively on software-related projects.

The Purpose¶

For this hackathon, our goal is increasing code stability to make the library steady as possible.

• Improve library stability and quality of the documentation
• Provide feedback to our customers

Organization¶

Hackathon duration is one week (from 8 October to 12 October). You should try to be in the office from 11 a.m. to 6 p.m. All communication activities will be at this time.

Each developer get own area of ​​responsibility:

Evgeny	build issues, objdetect
Ilya Lavrenov	imgproc
Daniil, Oleg	android, misc
Vadim	patches, misc
Vsevolod	documentation

Issues priorities in descending order:

• bug with provided solution (Patch with High priority)
• bug (from High to Low priorities)
• patch (implementing a new feature)
• feature

Hacker Guide¶

You should write 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 mantra.

Preferred sequence of actions:

• assign issue. You should choose some issue from the list of hackathon issues
• add test. This means that you have to have a failing test first. You can’t write any production code before ‘red’.
• fix problem. When you have compiling but failing test you can write some production code to satisfy the test
• commit changes to the repository. In commit message you should use #$$$$ template to link it with the issue.
• change issue status to Done. You should use commit:<6-digit git commit hash> template in issue updating. Please don't change Target version.

If in doubt, please, assign task to alexander.shishkov before or after commit.

If you want to discuss something with all Hackathon participants, please, use forum.

Links¶

• OpenCV hackathon slides
• About hackathon