OpenCPI tracks defects using the gitlab.com issue tracking system. The OpenCPI issues system is available here. No login or registration is required to browse the outstanding issues. Submitting issues from this page requires some means of identity, but does not require creating a gitlab account. This allows you to submit and track issues, and you will receive email notifications whenever anything happens to your issues, or issues you are watching.
Issues are commonly defects, but issues may be created for other reasons. The issue types that may be created or searched are:
Problems are used to indicate a negative experience that is not precise enough to be a specific defect.
e.g. "When I tried to do xxx, but it kept saying yyy".Bugs are specifically identified defects that try to contain enough information for them to be fixed.
e.g. "The xxx function creates the wrong result when the yyy option is selected".Improvements are incremental suggestions that extend functionality that exists.
e.g. "It would be great if the xxx function allowed for yyy to be set also"New features are capabilities that do not exist, but are desirable (by someone).
e.g. "OpenCPI should support writing workers in the FORTRAN and COBOL languages from the 1960s".Questions are used to get clarification on how to do something, which might be a documentation defect.
e.g. "How can I cause the xxx callback to happen every 10 seconds?"Ideas are imprecise topics thought worthy of discussion by someone.
e.g. "Does anyone think OpenCPI should support System-C for FPGA coding?"
For those that find submitting issues on gitlab problematic, issues may be submitted to the email address discuss at the domain lists.opencpi.org. Discussions, complaints or feature requests that do not require tracking are better submitted to this email list rather than the bug-tracking system.