Merge branch 'chore/standardize-readmes-2026-05' into main

Author: DavidsonGomes

CONTRIBUTING.md

@@ -0,0 +1,88 @@
+# Contributing to Evolution Go
+
+Thanks for your interest in contributing to Evolution Go! This document
+outlines how to contribute effectively.
+
+## Code of Conduct
+
+All contributors are expected to be respectful, inclusive, and professional.
+Harassment, discrimination, or abusive behavior will not be tolerated.
+
+## How to Contribute
+
+### Reporting Bugs
+
+1. Check existing [issues](https://github.com/EvolutionAPI/evolution-go/issues)
+   to avoid duplicates
+2. Open a new issue with:
+   - Clear, descriptive title
+   - Steps to reproduce
+   - Expected vs actual behavior
+   - Environment details (OS, version, dependencies)
+   - Logs or screenshots when relevant
+
+### Suggesting Features
+
+1. Open an issue describing:
+   - The problem you're trying to solve
+   - Your proposed solution
+   - Alternatives you considered
+2. Wait for maintainer feedback before starting implementation
+
+### Submitting Pull Requests
+
+1. Fork the repository
+2. Create a feature branch from `develop`:
+   ```bash
+   git checkout -b feat/your-feature-name
+   ```
+3. Make your changes following the project's coding standards
+4. Write or update tests for your changes
+5. Ensure all tests pass and the code lints clean
+6. Commit using [Conventional Commits](https://www.conventionalcommits.org/):
+   ```
+   feat: add new feature
+   fix: resolve bug in X
+   docs: update README
+   refactor: simplify Y
+   test: add coverage for Z
+   ```
+7. Push to your fork and open a PR against `develop`
+8. Fill out the PR template with context, testing notes, and screenshots if
+   applicable
+
+## Development Setup
+
+See [README.md](./README.md) for project-specific setup instructions.
+
+## Code Standards
+
+- Follow the existing code style of the project
+- Run linters and formatters before committing
+- Add tests for new features and bug fixes
+- Document public APIs and non-obvious behavior
+- Keep commits atomic and focused
+
+## Branch Strategy
+
+- `main` — stable production-ready code
+- `develop` — integration branch for upcoming releases
+- `feat/*`, `fix/*`, `chore/*` — short-lived branches off `develop`
+
+## Trademark Notice
+
+By contributing, you agree that your contributions will be licensed under the
+Apache License 2.0 (see [LICENSE](./LICENSE)). Trademarks and brand assets are
+governed separately by [TRADEMARKS.md](./TRADEMARKS.md).
+
+## Questions?
+
+- **Community**: [evolutionfoundation.com.br/community](https://evolutionfoundation.com.br/community)
+- **Documentation**: [docs.evolutionfoundation.com.br](https://docs.evolutionfoundation.com.br)
+- **Email**: suporte@evofoundation.com.br
+
+Thanks for helping make Evolution Go better!
+
+---
+
+© 2026 Evolution Foundation

LICENSE

@@ -1,3 +1,18 @@
+# Evolution Go License
+
+Evolution Go is licensed under the Apache License 2.0, with the following additional conditions:
+
+1. Evolution Go may be utilized commercially, including as a backend service for other applications or as an application development platform for enterprises. Should the conditions below be met, a commercial license must be obtained from the producer:
+
+   a. **LOGO and copyright information**: In the process of using Evolution Go's frontend components, you may not remove or modify the LOGO or copyright information in the Evolution Go console or applications. This restriction is inapplicable to uses of Evolution Go that do not involve its frontend components.
+
+   b. **Usage Notification Requirement**: If Evolution Go is used as part of any project, including closed-source systems (e.g., proprietary software), the user is required to display a clear notification within the system that Evolution Go is being utilized. This notification should be visible to system administrators and accessible from the system's documentation or settings page. Failure to comply with this requirement may result in the necessity for a commercial license, as determined by the producer.
+
+Please contact suporte@evofoundation.com.br to inquire about licensing matters.
+
+Apart from the specific conditions mentioned above, all other rights and restrictions follow the Apache License 2.0. Detailed information about the Apache License 2.0 can be found at http://www.apache.org/licenses/LICENSE-2.0.
+
+---
 
                                  Apache License
                            Version 2.0, January 2004
@@ -49,7 +64,7 @@
       "Contribution" shall mean any work of authorship, including
       the original version of the Work and any modifications or additions
       to that Work or Derivative Works thereof, that is intentionally
-      submitted to the Licensor for inclusion in the Work by the copyright owner
+      submitted to Licensor for inclusion in the Work by the copyright owner
       or by an individual or Legal Entity authorized to submit on behalf of
       the copyright owner. For the purposes of this definition, "submitted"
       means any form of electronic, verbal, or written communication sent
@@ -61,7 +76,7 @@
       designated in writing by the copyright owner as "Not a Contribution."
 
       "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by the Licensor and
+      on behalf of whom a Contribution has been received by Licensor and
       subsequently incorporated within the Work.
 
    2. Grant of Copyright License. Subject to the terms and conditions of
@@ -107,7 +122,7 @@
       (d) If the Work includes a "NOTICE" text file as part of its
           distribution, then any Derivative Works that You distribute must
           include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding any notices that do not
+          within such NOTICE file, excluding those notices that do not
           pertain to any part of the Derivative Works, in at least one
           of the following places: within a NOTICE text file distributed
           as part of the Derivative Works; within the Source form or
@@ -188,4 +203,6 @@
    distributed under the License is distributed on an "AS IS" BASIS,
    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    See the License for the specific language governing permissions and
-   limitations under the License.
+   limitations under the License.
+
+© 2026 Evolution Foundation

NOTICE

@@ -1,7 +1,18 @@
-Evolution Foundation
+Evolution Go
 Copyright 2026 Evolution Foundation
 
-This product includes software developed by Evolution Foundation.
+This product includes software developed by Evolution Foundation
+(https://evolutionfoundation.com.br).
 
 Trademark notice
-"Evolution Foundation" and "Evolution" are trademarks of Evolution Foundation. The Evolution Foundation logo, wordmark, and Evolution Foundation visual identity are governed by the Evolution Foundation Trademark and Brand Assets Policy included in this repository.
+"Evolution Foundation", "Evolution" and "Evolution Go" are trademarks of
+Evolution Foundation. The Evolution Go logo, wordmark, and visual identity
+are governed by the Trademark and Brand Assets Policy included in this
+repository (TRADEMARKS.md).
+
+Third-party attributions
+
+This product includes software developed by external contributors:
+
+- whatsmeow (https://github.com/tulir/whatsmeow) by Tulir Asokan, used as the
+  WhatsApp protocol library.