Unpublished reason? - Joomla! Forum - community, help and support
in,
http://extensions.joomla.org/extensions/406/details
i see:
---
editor's note
this extension has been unpublished following reason:
---
what reason? think because ver 1.0, shouldn't mentioned?
http://extensions.joomla.org/extensions/406/details
i see:
---
editor's note
this extension has been unpublished following reason:
---
what reason? think because ver 1.0, shouldn't mentioned?
possibly
viewtopic.php?f=262&t=416730
here need republish non-gpl extension:
in order developer keep non-gpl extension listed need relicense gpl.
you through add 2 elements each source file of program:
- copyright notice
- statement of copying permission, saying program distributed under terms of gnu general public license -
http://www.fsf.org/licensing/licenses/gpl-howto.html
- adding <license> tag header of extension xml file
- including copy of gpl license in distribution. not need copied user's server on install, must included in distribution.
- need state on website extensions distributed gpl license
- can't add conditions restricts or contradicts gpl license.
here need republish 1.0 extension
- need make extension @ least 1.5 legacy compatible. in normal cases, if extension written, shouldn't hard. in way know extension still maintained.
viewtopic.php?f=262&t=416730
here need republish non-gpl extension:
in order developer keep non-gpl extension listed need relicense gpl.
you through add 2 elements each source file of program:
- copyright notice
- statement of copying permission, saying program distributed under terms of gnu general public license -
http://www.fsf.org/licensing/licenses/gpl-howto.html
- adding <license> tag header of extension xml file
- including copy of gpl license in distribution. not need copied user's server on install, must included in distribution.
- need state on website extensions distributed gpl license
- can't add conditions restricts or contradicts gpl license.
here need republish 1.0 extension
- need make extension @ least 1.5 legacy compatible. in normal cases, if extension written, shouldn't hard. in way know extension still maintained.
Comments
Post a Comment