gunghogeoduck/osem-fcy
1
0
Fork 0
mirror of https://github.com/openSUSE/osem.git synced 2026-08-18 14:11:10 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Put the contribution guide into CONTRIBUTING.md

Browse source
This commit is contained in:
Henne Vogelsang 2014-04-25 18:13:20 +02:00
parent ee20ecce2f
commit b400a95476
2 changed files with 30 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

11
README.md
View file

@ -1,6 +1,7 @@
[![Build Status](https://travis-ci.org/openSUSE/osem.svg?branch=master)](https://travis-ci.org/openSUSE/osem)
[![Code Climate](https://codeclimate.com/github/openSUSE/osem.png)](https://codeclimate.com/github/openSUSE/osem)
[![Coverage Status](https://coveralls.io/repos/openSUSE/osem/badge.png)](https://coveralls.io/r/openSUSE/osem)
[![Security Status](https://hakiri.io/github/openSUSE/osem/master.svg)](https://hakiri.io/github/openSUSE/osem/master)
#OSEM
The Open Source Event Manager. An event management tool tailored to Free and Open Source Software conferences.
@ -54,13 +55,3 @@ We are using [rspec](http://rspec.info/)+[capybara](http://jnicklas.github.io/ca
```
bundle exec rake rspec
```
## Contributing
We are always looking for contributions to OSEM. Here is how you can:
* Fork the repository and make a pull-request with your changes
* Make sure that the test suite passes (we have travis enabled) before you request a pull and that you comply to our ruby styleguide (we make use of [hound-ci](https://houndci.com/)).
* Please make sure to mind what travis and hound tell you! :-)
* One of the OSEM maintainers will review your pull-request
* If you are already a contributor (means you're in the [group osem-committers](https://github.com/orgs/openSUSE/teams/osem-committers)) and you get a positive review, you can merge your pull-request yourself
* If you are not a contributor already please request a merge via the pull-request comments