ARSnova: powerpoint-edition needs you! If you are interested in helping, here is a short guide.
- First, fork and clone our repository.
- Create a topic branch.
- Remember to use test-driven development, it will make your live much easier.
- Make your changes. Be sure to provide clean commits and to write expressive commit messages.
- Check your style: All style settings are configured in this file. Import them and use ReSharper for "on-the-fly" code checking.
- Stay up to date with our repository: Rebase to our
staging
branch usinggit rebase
. - Push the changes to your topic branch.
- Run all the tests.
- Finally, submit a merge request.
If you don't feel like writing code, you could also update the documentation. And if you find any bugs, feel free to open a new issue.
To get your merge request accepted faster, you should follow our review process before submitting your request. Here is our list of dos and don'ts.
This is a no-brainer. Keep your branches up to date so that merges will never end up conflicting. Always test-merge your branches before submitting your pull requests. Ideally, your branches are fast-forwardable, but this is not a requirement.
Please check your code against our code guidelines defined with ReSharper.
Please take a look at our project file structure:
Business/
Business
Contract
Model
Common/
Common
Contract
Enum
Helpers
Resources
Communication/
Communication
Contract
Model
Installation/
Setup
Presentation/
Presentation
Configuration
Test/
Business/
Communication/
If questions regarding structures, patterns or frameworks occure, contact us or check out the thesis to this project (german only).
We are using NuGet as our package manager.
It all comes down to
- reviewing your own changes,
- keeping your commits clean and focused,
- and always staying up to date.
If you keep these things in mind, your merge requests will be accepted much faster. Happy coding!