This panel focuses on how people and companies participate in open source communities, including personal boundaries, inclusion, and different ways to contribute. It also addresses technical debt, shared responsibility, and how agencies cooperate while serving client needs.
The panel starts from an imbalance: businesses build on community-supported tools like Umbraco, so what do they owe in return? The answers are practical: pay employees for the time they spend contributing, encourage knowledge-sharing, and keep business value and community stewardship in balance.
Janae argues that clear boundaries are what make accountability possible, including keeping side projects and employer interests from overlapping in unhealthy ways. She also argues that companies, not only individuals, should carry the cost of sustaining the open source ecosystems they benefit from professionally.
Jen Wolke, who joined ProWorks in 2025, took part in the panel while at BlueModus.
Key takeaways
Open source participation is healthiest when people choose their own level of involvement instead of treating community work as an always-on obligation.
Newer community members benefit when experienced members explain project history and decisions instead of assuming everyone already knows the backstory.
Clients can become attached to older tools and patterns, which makes technical change harder even when a platform is moving toward better approaches.
Some agencies find that being active in an open source community improves business outcomes by making it easier to exchange ideas, find help, and manage overflow work.
Employers can support a healthier ecosystem by giving staff paid time to contribute, rather than expecting unpaid labor to sustain the tools the business relies on.
ProWorks is an Umbraco Platinum Partner. We build, upgrade and improve Umbraco sites, and help teams put AI to work in their CMS. Tell us what you're working on.
Jen Wolke tours useful Umbraco Marketplace packages, covering redirects, SEO, accessibility, responsive images, sustainability, CSP management, block previews, and content locking. She shows what each package does in the backoffice and when it helps.
This case study shows how ProWorks and Mold Inspection Sciences used component-based design in Umbraco to replace 12 legacy sites and simplify editing. Key results included cleaner content structure, better SEO and performance, and higher traffic and conversions after launch.
Headless on .NET Core - Umbraco Codegarden 2021 demonstrates a proof of concept for running Umbraco 9 headlessly with GraphQL and a Gridsome front end. It covers editor workflow, automatic rebuilds via notifications and GitHub Actions, and client-side search using Examine.