How do you currently organize community contributions and priorities?

[oronts-office]

Hi OpenDXP team,

I have been following OpenDXP for a while now and I honestly like what you are building. It is good to see a serious community-driven direction continuing in this space.

I work heavily in the Pimcore world myself, especially on bundles, integrations, platform architecture, custom development, and larger technical solutions. That is why I wanted to ask how you currently see contributions from external developers or agencies.

Can contributors already pick up open issues and work on pull requests? Are there current focus areas where support would be especially valuable, for example in the core, bundles, migrations, testing, documentation, or compatibility topics? And do you already have a preferred structure or process for people who want to contribute more regularly?

I would be happy to support where it brings real value and fits the direction of the project.

Respect again for the initiative. It is great to see OpenDXP getting real traction.

Best regards,
Oronts

[Refaat-alktifan]

Also adding a quick personal note here. I’m Refaat, founder of Oronts. I’ve been working a lot in the Pimcore ecosystem and really appreciate what you are building with OpenDXP. Happy to support where I can bring real value.

[solverat]

Hi @oronts-office / @Refaat-alktifan ,

thanks for reaching out. It's good to hear from someone with a strong background in the ecosystem, and we're happy to have you on board.

Where we are focused right now

Our main priority is keeping the core modern and stable. That means following Symfony best practices closely, ensuring OpenDXP never becomes a blocker in the broader Symfony ecosystem, and staying on top of performance improvements and security. On the longer-term roadmap, the database layer is a topic we'll be looking at more carefully.

Documentation is another area with room to grow, so contributions there are very much appreciated. This includes topics like best practices, hosting and server setup, which help new users get started more easily.

How contributions work

Bugfixes

Bug fixes are always welcome. Just open a PR and keep the changes focused. We review and test every PR ourselves (ok, at least we try :)), so smaller and targeted is better. Including a test is appreciated where it makes sense.

New features

New features require a discussion or issue to be opened before you start coding. This is about making sure no one invests time and money into something that might not fit the core. We have to maintain everything that lands in the codebase long-term, so we think carefully about what belongs in the core versus what might be better as a standalone bundle. A short conversation upfront saves everyone a lot of effort.

We'll be publishing more detailed contribution guidelines soon, but the above covers the essentials for now.

Best, the OpenDXP team

[HageMaster3108]

Hi @solverat thank you for these insights.
Can you let us know whether the long term plan is to have OpenDXP be 100% governed by Dachcom or is there potential for contributors to become part of the OpenDXP "board" (or whatever you want to name the group of people controlling the Roadmap and Strategy).
Thanks, Patrick