Skip to content
Browse files


  • Loading branch information...
dmajda committed Nov 4, 2013
1 parent fde219c commit b5d30cd3b9f2a3db932e17bc164d43b4a371ce8a
Showing with 87 additions and 0 deletions.
  1. +87 −0
@@ -0,0 +1,87 @@
YaST Contribution Guidelines

YaST is an open source project and as such it welcomes all kinds of
contributions. If you decide to contribute, please follow these guidelines to
ensure the process is effective and pleasant both for you and YaST maintainers.

There are two main forms of contribution: reporting bugs and performing code

Bug Reports

If you find a problem, please report it either using
or [GitHub issues](../../issues). (For Bugzilla, use the [simplified
if you don't have an account yet.)

If you find a problem, please report it either using
[Bugzilla]( or GitHub issues. We can't guarantee
that every bug will be fixed, but we'll try.

When creating a bug report, please follow our [bug reporting

Code Changes

We welcome all kinds of code contributions, from simple bug fixes to significant
refactorings and implementation of new features. However, before making any
non-trivial contribution, get in touch with us first — this can prevent wasted
effort on both sides. Also, have a look at our [development

To send us your code change, use GitHub pull requests. The workflow is as

1. Fork the project.

2. Create a topic branch based on `master`.

3. Implement your change, including tests (if possible). Make sure you adhere
to the [Ruby style

4. Make sure your change didn't break anything by building the RPM package
(`rake osc:build`). The build process includes running the full testsuite.

5. Publish the branch and create a pull request.

6. YaST developers will review your change and possibly point out issues.
Adapt the code under their guidance until they are all resolved.

7. Finally, the pull request will get merged or rejected.

See also [GitHub's guide on

If you want to do multiple unrelated changes, use separate branches and pull

Do not change the `VERSION` and `*.changes` files as this could lead to

### Commits

Each commit in the pull request should do only one thing, which is clearly
described by its commit message. Especially avoid mixing formatting changes and
functional changes into one commit. When writing commit messages, adhere to
[widely used

If your commit is related to a bug in Buzgilla or an issue on GitHub, make sure
you mention it in the commit message for cross-reference. Use format like
bnc#775814 or gh#yast/yast-foo#42. See also [GitHub
and [openSUSE abbreviation

Additional Information

If you have any question, feel free to ask at the [development mailing
list]( or at the
[#yast]( IRC channel on freenode.
We'll do our best to provide a timely and accurate answer.

0 comments on commit b5d30cd

Please sign in to comment.
You can’t perform that action at this time.