I’m Artur, Project Manager at SolDevelo, a software development company from Poland with 15+ years of market experience.
Currently, we provide technical support for DHIS2 for few Clients. We are also developing our own initiative, SolDevelo HIS, where DHIS2 will be a key component. As we want to deepen our expertise and take a more active role in the ecosystem, we are interested in becoming a Contributing Partner.
Could you please provide more information on:
The specific criteria and expectations for organizations in the contributing partner group
How the collaboration typically looks in practice (code, apps, or other forms of contribution)
The necessary steps to begin the onboarding process
Additionally, are there any current important issues or specific technical gaps in the roadmap where we could start contributing to support the platform’s development?
Our goal is to contribute our engineering capacity to the platform while building long-term specialized experience within our team.
It’s great that you’re looking into DHIS2 as one of the solutions you want to support your clients with. You’ve a global community and HISP network by your side, and your contributions will help implementations around the world.
I recommend checking out this short guide for a start: Contribute to the DHIS2 source code | DHIS2 Developer Portal. Most of the software development is use-case focused i.e. the features and improvements are based on what is actually being used and needed in the implementation field. This makes starting a discussion in the Development - Développement category within the community quite necessary to support the decision making and feedback directly with the community implementers and the DHIS2 software core team.
In addition to what @Gassim has recommended, you may wish to check out “What’s next in DHIS2,” from our 2025 Annual Conference. There are detailed discussions about priority efforts for software development, information about how to share your ideas with the core software team, etc.
@Scott Sure - thanks for sharing. I’ll reach out directly.
Thank you all for the warm welcome - we’re keen to understand the technical challenges (and real business problems) the community is facing and to explore how we can help.