Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define contribution guidelines #111

Open
mariospr opened this issue Jun 29, 2022 · 1 comment
Open

Define contribution guidelines #111

mariospr opened this issue Jun 29, 2022 · 1 comment
Labels
documentation Improvements or additions to documentation priority-high

Comments

@mariospr
Copy link
Member

We should perhaps write a Wiki page with some guidelines to contribute to this project such as the ones they have for WebKit [1] or Chromium [2], even though we might probably start a bit ligther.

In particular we should at least define how the process of landing code should look like such as selecting or creating an issue, providing changes in a PR following a certain convention, how the review process would look like, how code should be landed (e.g. no PR without an issue associated, having either PRs or commits should include a link to the issue...), what the desired coding style is...

Once these guidelines are in place it should be easier both for new people to provide contributions as for current developers to abide by the same rules (and/or evolve them if needed at the same time).

[1] https://webkit.org/contributing-code/
[2] https://chromium.googlesource.com/chromium/src/+/main/docs/contributing.md

@mariospr mariospr added documentation Improvements or additions to documentation priority-high labels Jun 29, 2022
@mariospr
Copy link
Member Author

This one is related: #110

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation priority-high
Projects
None yet
Development

No branches or pull requests

1 participant