Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rules for Posting on Premium Modules Issue Tracker #6

Open
ArchBlood opened this issue Jul 7, 2024 · 0 comments
Open

Rules for Posting on Premium Modules Issue Tracker #6

ArchBlood opened this issue Jul 7, 2024 · 0 comments
Assignees

Comments

@ArchBlood
Copy link
Contributor

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

  1. Be Respectful: Treat all members of the community with respect. Any form of harassment, discrimination, or inappropriate behavior will not be tolerated.

  2. 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.
  3. 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.

  4. 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.

  5. Attach Relevant Files: If applicable, attach screenshots, logs, or any other files that can help in diagnosing the issue or understanding the feature request.

  6. 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.

  7. Stay On Topic: Keep discussions relevant to the issue at hand. Avoid posting unrelated comments or questions.

  8. 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.

@ArchBlood ArchBlood pinned this issue Jul 7, 2024
@ArchBlood ArchBlood self-assigned this Jul 7, 2024
@GreenMeteor GreenMeteor deleted a comment from github-actions bot Jul 7, 2024
@GreenMeteor GreenMeteor locked as off-topic and limited conversation to collaborators Dec 2, 2024
@GreenMeteor GreenMeteor unlocked this conversation Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant