POWERLY CONTRIBUTOR GUIDELINES

Effective Date: March 1, 2025

Thank you for your interest in contributing to Powerly! We welcome contributions from developers worldwide. These guidelines outline the process and expectations for contributing to Powerly’s open-source projects.

1. How to Contribute

We accept contributions in the following areas:

Bug Fixes – Identify and resolve issues.
Feature Enhancements – Improve functionality.
Documentation Updates – Enhance clarity and accessibility.
Translations – Help us make Powerly more accessible globally.

To contribute:

Fork the repository from GitHub.
Create a feature branch.
Commit your changes with clear commit messages.
Submit a Pull Request (PR) and follow the PR template.
Engage in the review process with maintainers.

2. Code of Conduct

Powerly fosters a respectful, inclusive, and professional developer community. By contributing, you agree to:

Be respectful and professional in all communications.
No discrimination or harassment based on race, gender, or background.
Provide constructive feedback and help maintain a collaborative environment.
Follow Powerly’s contribution and coding standards.
Report Violations: If you encounter behavior that violates these principles, please report it to [email protected].

Failure to comply with these guidelines may result in warnings or removal from the project.

3. Contribution Licensing

By submitting a contribution, you agree to the following:

You retain copyright over your contributions.
You grant Powerly a non-exclusive, worldwide, royalty-free license to use, modify, and distribute your contributions.
Your contributions must not include third-party proprietary code without permission.

4. Issue Reporting

To report an issue:

Check existing issues to avoid duplicates.
Create a detailed issue report on GitHub Issues.
Provide logs, steps to reproduce, and expected behavior.
Issues are reviewed within 5 business days.

5. Development Best Practices

Follow the Powerly Coding Standards.
Ensure your code is well-documented and includes meaningful commit messages.
Write unit tests for new features.
Follow the branching strategy (e.g., main, develop, feature/*).
Pull Requests (PRs) are reviewed within 10 business days.

6. Contact & Support

For development-related discussions, join our Powerly Developer Community:

GitHub Discussions: https://github.com/powerly-ev/discussions
Developer Support: [email protected]

By contributing to Powerly, you acknowledge that you have read and agree to these guidelines.