On Github Issues and Pull Requests
Found a bug? Have a new feature to suggest? Want to add a new code examples to libra? or to contribute changes to the codebase? Make sure you're following these guidelines.
If there is an issue that persists, with Libra or any of its dependencies, we're here to support you.
Make sure your bug isn't already being worked on. Check the contribution queue and the issues backlog. If you don't see anything create an issue and we'll get back to you.
Make sure you provide us with enough information for us to reproduce the bug. What version of libra are you using? What IDE are you using to run your code? What does your dataset and instruction look like?
Provide us with a script to reproduce the issue. This can be a script that's loaded up onto GitHub gists. We also will accept google collaboratory links.
If possible, take a stab at fixing the bug yourself --if you can!
The more information you provide, the easier it is for us to validate that there is a bug and the faster we'll be able to take action. If you want your issue to be resolved quickly, following the steps above is crucial.
Requesting a Feature
Create an issue with the prefix feature:: and we'll get back to you immediately. If your change is fairly large and involves large structural changes shoot us an email at firstname.lastname@example.org
Provide a clear and detailed explanation of the feature you want and why it's important to add. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on library for Keras. It is crucial for Keras to avoid bloating the API and codebase.
Provide code snippets demonstrating the API you have in mind and illustrating the use cases of your feature. Of course, you don't need to write any real code at this point!
Adding new examples
Even if you don't contribute to the Libra source code, if you have an application of Libra that is concise and powerful, please consider adding it to our collection of examples, that will be collected in the tools folder of our main github repo.