To ensure a productive and respectful environment for all contributors, we are establishing a set of guidelines for posting issues on our premium modules issue tracker. These rules aim to streamline the process, foster constructive discussions, and ensure that all reported issues and feature requests are addressed efficiently.
Rules
-
Be Respectful: Treat all members of the community with respect. Any form of harassment, discrimination, or inappropriate behavior will not be tolerated.
-
Provide Clear and Detailed Information:
- Issue Title: Summarize the issue or feature request in a clear and concise title.
- Description: Provide a detailed description of the issue or feature request. Include steps to reproduce the issue, expected behavior, and actual behavior for bugs.
- Environment: Specify the environment in which the issue occurred, including the HumHub version, module version, PHP version, and any other relevant details.
-
Check for Duplicates: Before posting, search the issue tracker to see if the issue or feature request has already been reported. If it has, add your comments to the existing issue instead of creating a new one.
-
Use Proper Titles: Apply appropriate titles to your issue to help categorize it (e.g., Bug:, FR:, Enh:). This will help maintainers prioritize and manage issues more effectively.
-
Attach Relevant Files: If applicable, attach screenshots, logs, or any other files that can help in diagnosing the issue or understanding the feature request.
-
Follow Up: If your issue or feature request requires further clarification, follow up with additional information as needed. Be responsive to questions from maintainers and other contributors.
-
Stay On Topic: Keep discussions relevant to the issue at hand. Avoid posting unrelated comments or questions.
-
Respect the Contribution Guidelines: Adhere to the project's contribution guidelines and code of conduct.
Enforcement
Maintainers reserve the right to close or remove issues that do not comply with these rules. Repeated violations may result in further action, including being banned from the issue tracker.
Acknowledgment
By posting an issue or feature request, you acknowledge that you have read and agree to abide by these rules.
Feedback
We welcome feedback on these rules to ensure they are fair and effective. If you have any suggestions for improvement, please leave a comment on this issue.
Additional Notes:
Please ensure that any custom code modifications, theme overrides, or third-party extensions are mentioned when reporting issues. These can significantly affect behavior and are important for accurate troubleshooting.
If your issue is resolved or no longer relevant, please close the issue or leave a short comment so maintainers can keep the tracker organized. This helps us focus attention on active and unresolved items.
To ensure a productive and respectful environment for all contributors, we are establishing a set of guidelines for posting issues on our premium modules issue tracker. These rules aim to streamline the process, foster constructive discussions, and ensure that all reported issues and feature requests are addressed efficiently.
Rules
Be Respectful: Treat all members of the community with respect. Any form of harassment, discrimination, or inappropriate behavior will not be tolerated.
Provide Clear and Detailed Information:
Check for Duplicates: Before posting, search the issue tracker to see if the issue or feature request has already been reported. If it has, add your comments to the existing issue instead of creating a new one.
Use Proper Titles: Apply appropriate titles to your issue to help categorize it (e.g.,
Bug:,FR:,Enh:). This will help maintainers prioritize and manage issues more effectively.Attach Relevant Files: If applicable, attach screenshots, logs, or any other files that can help in diagnosing the issue or understanding the feature request.
Follow Up: If your issue or feature request requires further clarification, follow up with additional information as needed. Be responsive to questions from maintainers and other contributors.
Stay On Topic: Keep discussions relevant to the issue at hand. Avoid posting unrelated comments or questions.
Respect the Contribution Guidelines: Adhere to the project's contribution guidelines and code of conduct.
Enforcement
Maintainers reserve the right to close or remove issues that do not comply with these rules. Repeated violations may result in further action, including being banned from the issue tracker.
Acknowledgment
By posting an issue or feature request, you acknowledge that you have read and agree to abide by these rules.
Feedback
We welcome feedback on these rules to ensure they are fair and effective. If you have any suggestions for improvement, please leave a comment on this issue.
Additional Notes:
Please ensure that any custom code modifications, theme overrides, or third-party extensions are mentioned when reporting issues. These can significantly affect behavior and are important for accurate troubleshooting.
If your issue is resolved or no longer relevant, please close the issue or leave a short comment so maintainers can keep the tracker organized. This helps us focus attention on active and unresolved items.