dojoh-dev/reporter

This repository is the public issue entrypoint for the dojoh-dev organisation.

Use it to:

• report bugs,
• request enhancements,
• share reproducible problems in existing dojoh-dev projects.

Before opening an issue

Please make sure you:

1. Searched existing issues to avoid duplicates.
2. Used the correct issue form.
3. Included clear reproduction details (for bugs) or problem context (for features).
4. Shared expected vs actual behaviour.

How to report issues

1. Open the Issues tab.
2. Select the issue type that best matches your request.
3. Fill every required field in the template.
4. Submit one issue per problem/request.

High-quality reports are triaged faster and are much easier for maintainers to act on.

Response expectations

• Initial triage target: within 5 business days.
• Follow-up cadence: depends on priority, impact, and maintainer capacity.
• Requests for more info: if maintainers ask for details, please respond within 14 days to keep the issue active.

Issue hygiene and automation

To keep the tracker healthy and actionable:

• new issues are automatically labelled for triage,
• issues missing key details are labelled needs-information,
• inactive issues are marked stale and can be auto-closed after extended inactivity.

Security reports

Please do not report sensitive vulnerabilities in public issues. Use the repository/org security reporting channel when available.