Home

We are on IRC: #ozone-wayland

Developers

Instructions to set up development environment can be found in ReadMe file.

Get familiar with Git Hub. Useful pages:

1. https://help.github.com/articles/set-up-git
2. https://help.github.com/articles/fork-a-repo

We use GitHub's Pull Request mechanism to accept changes.

Coding Style:

1. [Coding style is the same as chromium] (http://www.chromium.org/developers/coding-style)

Commit-Message:

1. First line should be summary not exceeding 50 characters.
2. Second line should be a blank line.
3. Than an Explanatory text with lines not exceeding 72 characters.

Running Tests:

TODO

Submitting Pull Requests:

1. Start a new issue.
2. Find an OWNER and discuss whether the issue is valid. Ping us on IRC.
3. Branch repository, work on solution.
4. When ready for review, advertise the branch to other project members.
5. Get review from an OWNER, meaning an explicit LGTM.
6. It's quite common that initial solution is changed during review process. Separate final solution to semantically related commits and send pull request. Wait for owner to manage the merge.

Owners

1. Unless critical fix, nothing should go into master branch without review from one other OWNER.
2. Ensure that latest code always builds.
3. Ensure changes don't introduce any new regression and merge pull requests. Hopefully, we are able to soon run chromium tests. This should reduce the burden.
4. Guarantee integrity of whole project together with other owners.

Landing Pull Requests:

TODO

Rebasing process:

TODO