Rebranding a fork, fairly
This page is for designers who publish a fork under their own name. Rebranding is allowed under the GPL; erasing the people who made the original is not, and is unfair even where the law is unclear.
Change
| What | Where |
|---|---|
| The extension and design names | Folder, DesignExtensions[], SiteDesign documentation (Naming your theme extension) |
| The human name | ezinfo.php Name, extension.xml <name>, README |
| The package name | composer.json name, extra.ezpublish-legacy-extension-name |
| Your website and support | Info_url, homepage, support |
| Your own new work | Add your copyright line for it |
Keep
| What | Why |
|---|---|
LICENSE and the license of the code | The GPL requires it |
| Every existing copyright notice, in files and metadata | The GPL requires it; it is also the truth |
| Third-party notices | Their licenses require it |
| A "based on <original> by <author>" line in the README | Fairness; helps users find the origin |
Do not
- Imply that the original author or the Exponential project endorses your fork.
- Use the original's name as your product's name (Names and trademarks).
- Rewrite history to remove the original authors from commits.
Step by step
- Make the changes of the first table in one commit:
Renamed: <old> to <new>. - Add the "based on" line and your copyright line.
- Search for the old name:
git grep -n -i "<old name>"; change only identity, never copyright notices. - Release under your package name; tell users of the original how to switch, if your fork continues it.
Related pages
- Credits and attribution
- Contributing back upstream
- 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.