Contributing bundle fixes back
This page is for bundlers who find and fix problems while building their bundle. A fix you keep is a fix you re-apply at every release; a fix that is merged upstream arrives with the next release for everyone, you included.
Contents
- What to send back
- The kernel workflow
- Licensing of contributions
- Extensions and site packages
- Documentation
- What stays private
What to send back
| Found while bundling | Send to |
|---|---|
| A bug in the kernel or an installer | https://github.com/se7enxweb/exponential, issue or pull request |
| A missing option that would make bundling easier | an issue describing the need first |
| A default that is deliberate but wrong for your bundle | an issue with a clear justification; it may be a negative feature other sites rely on, so propose an option and expect several review rounds |
| A bug in an extension | the extension's repository |
| An improved or new site package | the package server's repository (Contribute your site package) |
| A mistake or gap in the documentation | a pull request to doc/ |
| A security problem | [email protected], privately, never as a public issue |
The kernel workflow
From Contributing code back and CONTRIBUTING.md:
- Fork the repository and create a branch for one change.
- Make the change, following the coding style.
- Commit with a subject that starts with what it does:
Added:,Updated:,Fixed:,Removed:orRenamed:. - Keep the file manifest current: every added, changed or removed file updates its line in
share/filelist.md5(make manifest-fix;make hooksinstalls the check). - Make sure the tests pass, update the documentation, push and open a pull request.
- Have a signed Contributor Licensing Agreement on file with 7x.
Licensing of contributions
"By contributing, you agree that your contributions will be licensed under the GNU General Public License, version
2.0 or later" and "a contribution to the core kernel needs your signed Contributor Licensing Agreement"
(CONTRIBUTING.md). Read the agreement before you sign; when your company holds the rights to its developers' work,
the company signs or gives its permission (Contributing code back).
Extensions and site packages
- Find the upstream of an extension before you fork it (Contributing extensions back upstream).
- Generic extensions you wrote for your bundle may be worth publishing (Publishing extensions from a bundle).
- "Built a site package? 7x and the Exponential Foundation strongly encourage you to submit it by pull request to the repository behind the package server, so every installation can offer it" (Site packages: start here).
Documentation
The help is free documentation under the GNU FDL 1.3; bundlers who write guides on top of it can send improvements to the original pages (Contributing docs and translations). A page about a bundling problem helps the next bundler.
What stays private
- Customer names, credentials, content and business rules.
- Your bundle's commercial terms.
- Anything you are not allowed to publish; check that you hold the rights before contributing.
Partners earn points for community work, including contributions (Earning points through community work).
Related pages
- Contribute extensions back
- Develop with Git
- Integrity checks
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.