Contribuições

Contribuindo para o Phalcon

Phalcon é um projeto de código aberto e depende fortemente dos esforços e contribuições voluntárias. Nós agradecemos as contribuições de todos!

Por favor, dedique alguns instantes a rever este documento para compreender o processo de contribuição e torná-lo tão eficiente quanto possível para todos. By following these guidelines, we can have faster resolution of issues, better communication, and we can all move the project forward!

The Phalcon source code (along with documentation, websites etc.) is stored in GitHub. You can browse our repositories in our organization page.

If you wish to contribute to Phalcon, you can do so by issuing a GitHub pull request.

Quando você cria uma pull request, nós temos um modelo bastante útil para ajudá-lo a descrever qual é o escopo da pull request. É muito importante e útil para a comunidade que você adicione testes ao seu pull request. Cada pull request será revisado por um colaborador principal (alguém com permissões para mesclar pull requests). Based on the type and content of the pull request, it could be:

• merged immediately or
• put on hold, where the reviewer requires changes (styling, tests etc.)
• put on hold, if discussion is necessary (community, core team etc.)
• rejected

NOTE: If your pull request is a new feature, it is best to discuss with the core team first, to ensure that it will align with the evolution of the framework.

NOTE: Please make sure that the target branch that you send your pull request is correct and that you have already rebased your code. Pull requests to the master branch are not allowed

Documentação

Se a programação em Zephir parece assustadora, há várias áreas para as quais você pode contribuir. Você pode sempre checar a documentação em busca de erros de tipografia ou contexto. Você também pode melhorar a documentação com mais exemplos nas respectivas páginas.

All you have to do is go to our docs repository, fork it, make the changes and send us a pull request.

NOTE: Note that changes to the docs repository are allowed only to the English documents (en folder).

Traduções

If you wish to contribute to Phalcon by translating our documents in your native tongue, you can utilize the excellent service of our friends at Crowdin. Our project is located here. Se o seu idioma não estiver listado, por favor nos envie uma mensagem para que possamos adicioná-lo.

Perguntas e Suporte

NOTE: We only accept bug reports, new feature requests and pull requests in GitHub. For questions regarding the usage of the framework or support requests please visit the official forum or our Discord server.

Lista de Problemas Encontrados

• Make sure you are using the latest released version of Phalcon before creating an issue in GitHub.
• Only bugs found in the latest released version of Phalcon will be addressed.
• We have a handy template when creating an issue to help you provide as much information for the core team to reproduce and address. Being able to reproduce a bug significantly reduces the time to find the cause and fix it. Scripts of even failing tests are more than appreciated. Please check how to create the reproducible tests page for more information.
• As part of your report, please include additional information such as the OS, PHP version, Phalcon version, web server, memory etc.
• If you’re submitting a Segmentation Fault error, we require a backtrace. Please check the Generating a Backtrace section for more information.

Geração de Backtrace

Sometimes due to Segmentation Fault error, Phalcon could crash some of your web server processes. Para nos ajudar a encontrar a causa desta falha de segmentação, precisaremos do backtrace do acidente.

Confira os seguintes links para obter instruções sobre como gerar o backtrace:

• Generating a gdb backtrace
• Generating a backtrace, with a compiler, on Win32
• Debugging Symbols
• Building PHP

Listas do Pull Request

• Pull requests to the master branch are not accepted. Please fork the repository and create your branch from the necessary “source” branch, for instance 4.0.x and if need be rebase your branch before submitting your pull request. If there are collisions, we will ask you to rebase your branch again.
• Add tests to your pull request or adjust existing ones. This is very important since it helps justify your pull request. Please check our testing page for more information on how to set up a test environment and how to write tests.
• Since Phalcon is written in Zephir, please do not submit commits that modify the C generated files directly
• Phalcon follows a specific coding style. Please install the editorconfig plugin in your favorite IDE to take advantage of the supplied .editorconfig file that comes with this repository and not to have to worry about coding standards. All tests (PHP code), follow the PSR-12 standard
• Remove any change to ext/kernel, *.zep.c and *.zep.h files before submitting the pull request
• More information here.

Before submitting new functionality, please open a NFR as a new issue on GitHub to discuss the impact of including the functionality or changes in the core extension. Uma vez aprovada a funcionalidade, certifique-se de que sua PR contenha o seguinte:

• An update to the CHANGELOG.md
• Unit Tests
• Documentation or Usage Examples

Obtendo Suporte

If you have any questions about how to use Phalcon, please see the support page.

Solicitando Recursos

If you have any changes or new features in mind, please fill an NFR.

Obrigado!

<3 Phalcon Team