Collaborating and Submitting Changes

The information next explains how developers and owners can help each other to contribute for the Ozone-Wayland. In general, the contribution process follows the Chromium guidelines (with the exception that we don't have the gcl or git-cl tools).

Developers

Submitting pull requests:

1. Start a new issue. Add description about the problem and platform. Please do add any relevant bug link (In case your project is using Oz-WL) which has any prior discussions that could help us understand the problem.
2. Find an OWNER and discuss whether the issue is valid.
3. Branch repository, work on solution.
4. When ready for review, add link to your branch in the comments section of issue created in step1.
5. Get review from an OWNER, meaning an explicit LGTM. If this is your first contribution, please add your name to AUTHORS list.
6. It's quite common that the initial solution is changed during review process. Separate final solution to semantically related commits and send a pull request. Wait for owner to manage the merge.

Coding style:

1. Coding style is the same as Chromium's.

Commit message:

1. First line should be a summary not exceeding 72 characters.
2. Second line should be a blank line.
3. Then an explanatory text.

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.