-
Notifications
You must be signed in to change notification settings - Fork 2
Contacts
Different types of questions or discussions correspond to different avenues of communication; check the descriptions below to ensure you choose the right method.
If you identify bugs, have suggestions for improvements, or a question specific to one package, you can open an issue on GitHub.
Before opening an issue, check if other users have reported similar issues by searching across the GitHub repository.
When filing an issue, please make sure to include enough information for another person to understand the issue.
Describe exactly what you were doing or are trying to do, and exactly what, if anything, went wrong. If following a tutorial or online instructions provide a link to the specific instructions.
- Use a descriptive headline or subject line. Bad: “rviz doesn’t work”. Good: “Rviz crashing looking for missing .so after latest apt update”
- Include information about the exact platform, software, versions, and environment relevant to the problem.
- Any warnings or errors. Cut and paste them directly from the terminal window to which they were printed.
- In case of a bug consider providing a short, self contained, correct, example.
- When discussing any compiling/linking/installation issues, also provide the compiler version.
When you feel comfortable enough to suggest a specific change directly to the code, you can submit a pull request. Pull requests are welcome for every valuable improvement.
If you’d like to contact us privately on any kind of topic, you can email us directly at costadavid@dei.unipd.it.