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
Help move an XWiki feature, bug fix or open-source improvement forward by funding
professional development work contributed through the normal XWiki community process.
Already have a JIRA issue? Just send the link.
The first step is determining whether the requested work can provide broader value
and is suitable for open-source development.
Finance functionality that could provide broader value to XWiki users instead of remaining specific to one deployment. Improve an existing community extension or develop reusable functionality that makes more sense outside XWiki Standard.
A funded improvement moves through the same technical discussion, implementation,
testing and review process as other open-source XWiki contributions.
Send an existing XWiki JIRA issue, forum discussion or a description of the requirement. Agnease reviews feasibility, current functionality, related issues, architecture and the most appropriate implementation path. Significant changes are discussed through the appropriate XWiki community channels before substantial implementation begins. Agnease prepares an engineering estimate. One organization can finance the work or several interested organizations can potentially share the cost. Implementation can include code, automated tests, documentation, accessibility, security, migration and compatibility considerations. 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 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.
When an improvement has broader value, contributing it upstream can reduce
long-term maintenance while benefiting other XWiki users.
An upstream feature can eliminate private customization that would otherwise need to be maintained through future XWiki upgrades. Functionality maintained as part of XWiki or an open-source extension has a clearer path through future releases. The implementation can be reviewed and improved by experienced XWiki contributors. If several organizations need the same functionality, they can potentially finance the development together. Useful functionality can benefit other XWiki users rather than remaining locked inside one private deployment. Organizations can optionally be credited for supporting an open-source improvement, or remain anonymous.
Proposed improvements can be listed here while technical discussion,
estimates and interested organizations are identified.
Add native light and dark Color Theme selection to XWiki, with an automatic mode that follows the browser or operating-system color preference.
Funding target:
To be estimated after technical discussion
Send an existing JIRA issue, forum discussion or describe the improvement you need.
The first step is determining whether it is technically feasible and suitable for
open-source contribution.
The implementation work is led by Alex Cotiugă, an active XWiki committer
with more than a decade of XWiki development experience, including 7.5 years
working at XWiki SAS.
This experience helps proposed improvements be approached with an understanding
of XWiki architecture, development practices, testing expectations and the
upstream contribution process. It does not provide special authority over
whether a contribution is accepted.
No. Funding covers Agnease's development work. Contributions remain subject to the normal XWiki discussion and review process. Yes. Existing XWiki issues are ideal candidates. Send the JIRA link and Agnease can assess it. Yes. Co-funding allows several organizations interested in the same improvement to potentially share the development cost. Yes. Interest from several users can help identify improvements worth estimating and developing. 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. Work accepted into an upstream open-source project is contributed under that project's applicable open-source licence. Yes, if desired. Sponsors can also remain anonymous. Yes. If a requirement is organization-specific and does not make sense upstream, it can be evaluated as normal custom XWiki development.
Send the issue or requirement. The first step is simply determining whether
it is feasible, reusable and suitable for open-source contribution.
Open-source XWiki development
Fund an XWiki Improvement
What can be funded?
Features and improvements
Open-source extensions
From idea to upstream contribution
Submit the idea
Technical assessment
Community alignment
Estimate and funding
Development
Upstream contribution
Funding development does not buy acceptance
Why contribute upstream instead of maintaining another customization?
Reduce custom maintenance
Improve long-term compatibility
Benefit from community review
Share development costs
Give back to the ecosystem
Optional sponsor recognition
Improvements seeking interest or funding
Seeking interest / funding
Automatic Light/Dark Theme Switching for XWiki
Is there an XWiki issue you would like to move forward?
Development led by an experienced XWiki contributor
Frequently asked questions
Does paying guarantee that the improvement will be included in XWiki?
Can I fund an existing JIRA issue?
Can several organizations finance the same improvement?
Can I propose something without committing money?
What happens if the feature does not belong in XWiki Standard?
Who owns the resulting code?
Can my organization be publicly credited?
Can Agnease implement private functionality instead?
Have an XWiki issue that needs attention?