Skip to main content
This guide covers best practices and conventions for contributing to the Oro application source code, user interface translations, and documentation. It also describes how to contact the Oro community and support team, and offers an insight into the Oro application release process.

​
Contact the community

Join the Oro community and contribute to the open-source OroCommerce Community Edition.

Stack Overflow

Direct issues you encounter when configuring, extending, or customizing Oro applications to Stack Overflow. Use the tags [orocommerce], [orocrm], or [oroplatform].

GitHub

Fork Oro repositories and contribute to the source code on GitHub. Use the GitHub Issue Tracker for OroCommerce, OroCRM, or OroPlatform.

Slack

Join the community Slack channel to ask questions and get advice from fellow community members.

Twitter

Follow the Oro team on Twitter for information on upcoming features and events.

Facebook

Follow Oro’s Facebook pages for announcements, latest news, publications, and upcoming events.

LinkedIn

Follow OroInc on LinkedIn for ecommerce posts, Oro news, and webinar links.

​
Contribute to source code, translations, and documentation

The following guidelines and recommendations enable the community to synchronize actions and provide a blueprint for seamless, non-intrusive collaboration.

Use version control

Learn about the Git-based version control conventions used across all Oro projects and how to communicate context in every commit.

Follow code style

Code style conventions used in all Oro projects for PHP, JavaScript, SCSS, and more.

Set up a development environment

Best practices for configuring a local Oro development environment.

Contribute to translations

Oro applications support multiple languages. Learn how to join the translation team on Crowdin and submit translations.

Contribute to documentation

Learn about the documentation structure, RST directives, and the workflow for publishing new topics.
Please read and sign the Contributor License Agreement (CLA) before suggesting changes to the source code or documentation.

​
Report issues

If you encounter any issues with your Oro application or spot inaccuracies in documentation, please inform us.
We recognize how important it is to help protect your privacy and security. Never post security issues publicly — use the dedicated security reporting process instead.

Report an issue

Submit a bug report or documentation issue to the appropriate GitHub issue tracker.

Report a security issue

Contact the Oro security team privately. Never post security issues publicly — use the dedicated security reporting process.

​
Release versions and dates

Refer to the Release Process topic to learn more about Oro’s versioning strategy, release and support cycle, and upgrade recommendations.

​
Backward compatibility promise

Refer to the Backward Compatibility Promise topic to learn about what compatibility guarantees Oro provides across releases.

Build docs developers (and LLMs) love

Get started for freeTalk to us