Reporting problems

Please use Github issue tracker if you think you found a bug or problem in Nagira. Also please make sure that such issue was not registered yet, or was not yet fixed in newer versions of Nagira (look at the closed issues as well as open ones).

However, if you think issue is related to the security and disclosing the issue can harm current users, please refrain from submitting open bug report, instead please feel free to write private email to me (dmytro.kovalov@gmail.com) with the description of the problem (and possible ways to fix it, if you aware of any).

Contributing

What if you have already fix for the bug, or you have developed new feature, or simply you have great idea how to improve the code?

Before starting development, submitting pull request for the feature or bug-fix please make sure to check issue tracker (above).

Here are steps if you want contribute to the project:

• Fork it
• Create your feature branch (git checkout -b my-new-feature)
• Commit your changes (git commit -am 'Add some feature')
• Push to the branch (git push origin my-new-feature)
• Create new Pull Request

Guidelines

There's a simple list of guidelines about namespacing of the RESTful routes. Please see API_NAMESPACING

That's too difficult ...

Then simply drop me an email at dmytro.kovalov@gmail.com