Bug fixes
Help move an existing XWiki bug forward when it is important to your organization or users.
- Usability and rendering issues
- Administration problems
- Accessibility improvements
- Authentication or permission issues
- Compatibility problems
Open-source XWiki development
Fund an XWiki Improvement
Help move an XWiki feature, bug fix or open-source improvement forward by funding professional development work contributed through the normal XWiki community process.
- Existing JIRA issues
- New improvements
- Community extensions
- Individual or shared funding
Already have a JIRA issue? Send us the link.
What can be funded?
The first step is determining whether the requested work can provide broader value and is suitable for open-source development.
Features and improvements
Finance functionality that could provide broader value to XWiki users instead of remaining specific to one deployment.
- User interface improvements
- New platform capabilities
- Administration features
- Workflow improvements
- New configuration options
Open-source extensions
Improve an existing community extension or develop reusable functionality that makes more sense outside XWiki Standard.
- Existing XWiki Contrib extensions
- Reusable new functionality
- Maintenance and compatibility work
- Tests and documentation
From idea to upstream contribution
A funded improvement follows the same technical discussion, implementation, testing and review process as other open-source XWiki contributions.
Submit the idea
Send an existing XWiki JIRA issue, forum discussion or a description of the requirement.
Technical assessment
Agnease reviews feasibility, current functionality, related issues, architecture and the most appropriate implementation path.
Community alignment
Significant changes are discussed through the appropriate XWiki community channels before substantial implementation begins.
Estimate and funding
Agnease prepares an engineering estimate. One organization can finance the work or several interested organizations can potentially share the cost.
Development
Implementation can include code, automated tests, documentation, accessibility, security, migration and compatibility considerations.
Upstream contribution
The resulting work is proposed through the normal XWiki contribution and review process.
Funding provides engineering capacity, not a shortcut around the community process. One organization can finance the work, several organizations can share the cost, or an improvement can first be listed to identify wider interest.
Funding development does not buy acceptance
Funding covers Agnease's professional engineering work. It does not bypass the XWiki community development process and does not guarantee that a proposed feature will be accepted upstream in its original form.
Significant changes may require prior discussion, architectural adjustments or community review. Agnease aims to identify these risks before substantial funded development begins and performs agreed work following XWiki development conventions, testing expectations, compatibility requirements and the normal contribution process.
Why contribute upstream instead of maintaining another customization?
When an improvement has broader value, contributing it upstream can reduce long-term maintenance while benefiting other XWiki users.
Reduce custom maintenance
An upstream feature can eliminate private customization that would otherwise need to be maintained through future XWiki upgrades.
Improve long-term compatibility
Functionality maintained as part of XWiki or an open-source extension has a clearer path through future releases.
Benefit from community review
The implementation can be reviewed and improved through the normal XWiki contribution and review process.
Share development costs
If several organizations need the same functionality, they can potentially finance the development together.
Give back to the ecosystem
Useful functionality can benefit other XWiki users rather than remaining locked inside one private deployment.
Optional sponsor recognition
Organizations can optionally be credited for supporting an open-source improvement, or remain anonymous.
Improvements seeking interest or funding
Explore XWiki improvements currently being assessed for community interest, technical feasibility and potential funding.
Seeking interest / funding
Automatic Light/Dark Theme Switching for XWiki
Add native light and dark Color Theme selection to XWiki, with an automatic mode that follows the browser or operating-system color preference.
- Administrators configure the light and dark Color Themes
- Users choose System / Automatic, Light or Dark
- System mode follows the prefers-color-scheme browser preference
- Anonymous-user behaviour and preference persistence need to be defined
- Implementation requires upstream technical discussion, tests and documentation
Funding target: To be estimated after technical discussion
Frequently asked questions
Does paying guarantee that the improvement will be included in XWiki?
No. Funding covers Agnease's development work. Contributions remain subject to the normal XWiki discussion and review process.
Can I fund an existing JIRA issue?
Yes. Existing XWiki issues are ideal candidates. Send the JIRA link and Agnease can assess it.
Can several organizations finance the same improvement?
Yes. Several organizations interested in the same improvement can potentially share the development cost.
Can I propose something without committing money?
Yes. Interest from several users can help identify improvements worth estimating and developing.
What happens if the feature does not belong in XWiki Standard?
It may be more appropriate for an existing open-source extension, a new reusable extension or private development. Agnease can help identify the appropriate path.
Who owns the resulting code?
Work accepted into an upstream open-source project is contributed under that project's applicable open-source licence.
Can my organization be publicly credited?
Yes, if desired. Sponsors can also remain anonymous.
Can Agnease implement private functionality instead?
Yes. If a requirement is organization-specific and does not make sense upstream, it can be evaluated as normal custom XWiki development.
Have an XWiki issue that needs attention?
Send the issue or describe the improvement. A complete specification is not required; the first step is determining whether the idea is feasible and suitable for open-source contribution.