Skip to content
CONTRIBUTING.md 2.63 KiB
Newer Older
Henne Vogelsang's avatar
Henne Vogelsang committed
# Request for contributions
We are always looking for contributions to the Open Build Service. Read this guide on how to do that. 

In particular, this community seeks the following types of contributions:

Henne Vogelsang's avatar
Henne Vogelsang committed
* code: contribute your expertise in an area by helping us expand the Open Build Service
Henne Vogelsang's avatar
Henne Vogelsang committed
* ideas: participate in an issues thread or start your own to have your voice heard.
Henne Vogelsang's avatar
Henne Vogelsang committed
* copy editing: fix typos, clarify language, and generally improve the quality of the content of the Open Build Service
# How to contribute code
* Prerequisites: familiarity with [GitHub Pull Requests](https://help.github.com/articles/using-pull-requests.)
Henne Vogelsang's avatar
Henne Vogelsang committed
* Fork the repository and make a pull-request with your changes
  * Please make sure to mind what our test suite in [travis](https://travis-ci.org/openSUSE/open-build-service) tells you! :-)
  * Please increase our [code coverage](https://codeclimate.com/github/openSUSE/open-build-service) by your pull request!

Henne Vogelsang's avatar
Henne Vogelsang committed
* One of the Open Build Service maintainers will review your pull-request
Henne Vogelsang's avatar
Henne Vogelsang committed
  * If you are already a contributor (means you're in the [open-build-service team](https://github.com/orgs/openSUSE/teams/open-build-service)) and you get a positive review, you can merge your pull-request yourself
  * If you are not a contributor already the reviewer will merge your pull-request

# How to contribute issues
* Prerequisites: familiarity with [GitHub Issues](https://guides.github.com/features/issues/).
* Enter your issue and a member of the [open-build-service team](https://github.com/orgs/openSUSE/teams/open-build-service) will label and prioritize it for you.

We are using priority labels from **P0** to **P4** for our issues. So if you are a memer of the [open-build-service team](https://github.com/orgs/openSUSE/teams/open-build-service) you are supposed to
* P0: Critical Situation - Drop what you are doing and fix this issue now!
* P1: Urgent - Fix this next even if you still have other issues assigned to you.
* P2: High   - Fix this after you have fixed all your other issues.
* P3: Medium - Fix this when you have time.
* P4: Low  - Fix this when you don't see any issues with the other priorities.

Henne Vogelsang's avatar
Henne Vogelsang committed
# Conduct
Henne Vogelsang's avatar
Henne Vogelsang committed
The Open Build Service is part of the openSUSE project. We follow all the [openSUSE Guiding
Henne Vogelsang's avatar
Henne Vogelsang committed
Principles!](http://en.opensuse.org/openSUSE:Guiding_principles) If you think
Henne Vogelsang's avatar
Henne Vogelsang committed
someone doesn't do that, please let any of the [openSUSE
owners](https://github.com/orgs/openSUSE/teams/owners) know!
Henne Vogelsang's avatar
Henne Vogelsang committed

# Communication
GitHub issues are the primary way for communicating about specific proposed
changes to this project. If you have other problems please use one of the other
[support channels])(http://openbuildservice.org/support/)