Clone this wiki locally
A hackathon is an event in which computer programmers and others in the field of software development collaborate intensively on software-related projects.
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
Hackathon duration is one week. For itseez employees – 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.
Issues priorities in descending order:
- bug with provided solution (Patch with High priority)
- bug (from High to Low priorities)
- patch (implementing a new feature)
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 to yourself. You should choose some issue from the list of hackathon issues
- reproduce problem first, if it’s a bug. If possible, add the test that reproduces the problem.
- fix problem. When you have compiling but failing test you can modify OpenCV 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 the ticket to vadim pisarevsky before or after commit.