Make sure that you have reviewed and agreed to the code of conduct and license before you contribute.
Your questions, ideas, proposed improvements, and generic experiences of using SPERR all make good contributions! You're welcome to discuss them in the discussion board.
If you encounter unexpected behaviors and build/runtime errors of SPERR, or if you spot a substandard practice in programming, please open an issue.
If you have some code that improves SPERR in functionality, performance, reliability, etc., please submit a PR with your improvements.