Feel free to submit bugs via Issue Tracker, but PLEASE READ THE FOLLOWING FIRST: RP2 stores logs and outputs locally on the user's machine and doesn't send this data elsewhere. Logs, inputs and outputs can be useful to reproduce a bug, so a user can decide (or not) to share them to help fix a problem. If you decide to share this information, be mindful of what you post or send out: stack traces are typically free of personal data, but RP2 logs, inputs and outputs, while very useful to reproduce an issue, may contain information that can identify you and your transactions. Before posting such data publicly or even sending it privately to the maintainers of RP2, make sure that:
- the data is sanitized of personal information (although this may make it harder to reproduce the problem), or
- you're comfortable sharing your personal data.
Logs are stored in the log/ directory and each file name is appended with a timestamp. Outputs are stored in the output/ directory or where specified by the user with the -o option.
Read the developer guide, which describes setup instructions, development workflow, design principles, source tree structure, plugin architecture, etc.
Feel free to submit pull requests. Please follow these practices:
- follow the RP2 design guidelines
- follow the PEP 8 coding standard;
- add unit tests for any new code;
- ensure your commits are atomic (one feature per commit);
- write a clear log message for your commits.
Read about the RP2 Ecosystem.