Difference between revisions of "Forked Extensions"
From Joomla! Documentation
(Marked this version for translation) |
m (Content updated) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 2: | Line 2: | ||
{{RightTOC}}<translate><!--T:1--> | {{RightTOC}}<translate><!--T:1--> | ||
"In software engineering, a project fork happens when developers take a legal copy of source code from one software package and start independent development on it, creating a distinct piece of software."<ref>http://en.wikipedia.org/wiki/Fork_(software_development)</ref> | "In software engineering, a project fork happens when developers take a legal copy of source code from one software package and start independent development on it, creating a distinct piece of software."<ref>http://en.wikipedia.org/wiki/Fork_(software_development)</ref> | ||
| − | + | The JED supports the original project developer whenever possible to maintain the integrity of the listings and also supports developers who are building and innovating on the Joomla platform.</translate> | |
<translate><!--T:2--> | <translate><!--T:2--> | ||
| − | To have a forked | + | To have a forked extension listed in the JED it must meet additional requirements listed below:</translate> |
<translate>==General requirements== <!--T:3--> | <translate>==General requirements== <!--T:3--> | ||
| Line 18: | Line 18: | ||
<translate>==Copyright notices== <!--T:7--></translate> | <translate>==Copyright notices== <!--T:7--></translate> | ||
<translate><!--T:8--> | <translate><!--T:8--> | ||
| − | Forked project must respect copyright law | + | Forked project must respect copyright law: |
| − | * | + | * The original copyright holder must be acknowledged in the code files. |
| − | + | * The XML installer file must include a comment on the original extension name. | |
| + | * It's considered good practice to provide a link to the original extension URL. | ||
| + | </translate> | ||
| − | + | <translate>== Forked extension names == <!--T:10--> | |
| − | + | * The extension name needs to be changed so it is very clear that this is a separate project.</translate> | |
| − | |||
| − | <translate>== Forked extension | ||
| − | The extension name needs to be changed so it is very clear that this is a separate project</translate> | ||
<translate><!--T:11--> | <translate><!--T:11--> | ||
| − | * | + | * The forked extension cannot include the original extension's name. |
| − | * | + | * The JED does not allow forked projects by new developers to build on the name of the original developer without permission.</translate> |
<translate>==Version structure== <!--T:12--></translate> | <translate>==Version structure== <!--T:12--></translate> | ||
<translate><!--T:13--> | <translate><!--T:13--> | ||
| − | * '''Separated paths''': development of the extension follows | + | * '''Separated paths''': development of the extension follows its own path, and will not be based on the original extension updates after listing. |
* '''Unique version structure''': version numbering must clearly indicate a new project.</translate> | * '''Unique version structure''': version numbering must clearly indicate a new project.</translate> | ||
| Line 40: | Line 39: | ||
If the original extension is listed on the Joomla! Extensions Directory:</translate> | If the original extension is listed on the Joomla! Extensions Directory:</translate> | ||
<translate><!--T:16--> | <translate><!--T:16--> | ||
| − | * '''Time protection''': the | + | * '''Time protection''': the fork will only be considered for listing if the original extension has been listed for more than 3 months.</translate> |
<translate><!--T:17--> | <translate><!--T:17--> | ||
| − | * '''Significant change''': forked project must represent a significant code improvement, either in features or security and structure.</translate> | + | * '''Significant change''': the forked project must represent a significant code improvement, either in features or security and structure.</translate> |
<translate><!--T:18--> | <translate><!--T:18--> | ||
| − | + | * The amount of functionality to be added is determined on a case by case basis and is at the sole discretion of the Joomla! Extensions Directory team and Open Source Matters.</translate> | |
| − | |||
<translate><!--T:19--> | <translate><!--T:19--> | ||
| − | Its considered a good practice to link to the original extension in the JED description.</translate> | + | * Its considered a good practice to link to the original extension in the JED description.</translate> |
<translate>==Additional reading== <!--T:20--></translate> | <translate>==Additional reading== <!--T:20--></translate> | ||
<translate><!--T:21--> | <translate><!--T:21--> | ||
| + | * See more on the JED website: [http://extensions.joomla.org/support/knowledgebase/item/forked-extensions Forked Extensions] | ||
* Directory TOS: [http://extensions.joomla.org/tos : Extensions and Forks] | * Directory TOS: [http://extensions.joomla.org/tos : Extensions and Forks] | ||
* FAQ: [[S:MyLanguage/Extensions_and_GPL|Extensions and GPL]]</translate> | * FAQ: [[S:MyLanguage/Extensions_and_GPL|Extensions and GPL]]</translate> | ||
Revision as of 08:48, 19 August 2015
"In software engineering, a project fork happens when developers take a legal copy of source code from one software package and start independent development on it, creating a distinct piece of software."[1]
The JED supports the original project developer whenever possible to maintain the integrity of the listings and also supports developers who are building and innovating on the Joomla platform.
To have a forked extension listed in the JED it must meet additional requirements listed below:
General requirements[edit]
An extension that is derived from another extension will only be listed under the following conditions :
- License permission: the original extension license allows this or the current developer of the original extension has specifically authorized it if the license does not.
- Separated project: it is very clear that this is a separate project (e.g. extension is renamed and have a new version scheme).
- Intent to develop and support: forked project must exhibit an intent to develop and support the new product.
Copyright notices[edit]
Forked project must respect copyright law:
- The original copyright holder must be acknowledged in the code files.
- The XML installer file must include a comment on the original extension name.
- It's considered good practice to provide a link to the original extension URL.
Forked extension names[edit]
- The extension name needs to be changed so it is very clear that this is a separate project.
- The forked extension cannot include the original extension's name.
- The JED does not allow forked projects by new developers to build on the name of the original developer without permission.
Version structure[edit]
- Separated paths: development of the extension follows its own path, and will not be based on the original extension updates after listing.
- Unique version structure: version numbering must clearly indicate a new project.
Protection of the original listing[edit]
If the original extension is listed on the Joomla! Extensions Directory:
- Time protection: the fork will only be considered for listing if the original extension has been listed for more than 3 months.
- Significant change: the forked project must represent a significant code improvement, either in features or security and structure.
- The amount of functionality to be added is determined on a case by case basis and is at the sole discretion of the Joomla! Extensions Directory team and Open Source Matters.
- Its considered a good practice to link to the original extension in the JED description.
Additional reading[edit]
- See more on the JED website: Forked Extensions
- Directory TOS: : Extensions and Forks
- FAQ: Extensions and GPL