[TYPO3-english] Releasing TYPO3 6.2 LTS under GPL Version 3

Mon Jun 17 07:59:42 CEST 2013

Hi

I have some more thoughts why TYPO3 6..2.0 Final should be released
actually as TYPO3 7.0 LTS!

   1. The TYPO3 6.2 LTS / TYPO3 7.0 LTS Version would be in place for a
   couple of years and during this time hopefully NEOS will get a bit more
   mature to be used by a bigger crowd as right now!
   2. The TYPO3 6.2 LTS / TYPO3 7.0 LTS Version is starting a new area in
   many ways as many things which were working before Version 6 or before
   Version 6.2 even are no more working like before! The Code of many
   extensions needs to be changed anyway and those extensions could be
   rereleased under GPLv3 too to be again full compatible with TYPO3 6.2 LTS /
   TYPO3 7.0 LTS
   3. Extension Developers, Designers, Packagers and Integrators who wold
   like to get their stuff also being easier to use or transferable to NEOS
   when it would be ready would benefit from the change to GPLv3.

@Georg

I am aware that the relicensing is not easy, but NOW is the right time do
ask all those contributors incl. myself, if they are OK with the switch to
GPLv3.

This could be done either in written, email to contact the people or
perhaps even in adding a field in the extension repository or git like you
do already with the contributor license!

BUT it has to be separate from this contributor license which quite a lot
of people not will sign.

You could set a timeframe until people need to answer the request. IMHO Now
is the time in doing this and simply creating a MAJOR Version TYPO3 7.0 LTS
out of Typo3 6.2 to make the change also very visible to the public!

Andi

On Mon, Jun 17, 2013 at 12:40 PM, Andreas Becker <ab.becker at web.de> wrote:

> Hi All
>
> The goal is to make TYPO3 more user-friendly. Right? To create a bigger
> customer base? Right.
> etc.
>
> One very important factor in doing this would be to provide packages.
> Fabien is already trying to improving the Introduction Package using
> Bootstrap, Kay with Themes and Claus Due who provides lots of bootstrap
> based Extensions and Joey with Grid Elements and many more people who use
> meanwhile bootstrap and other modern coding approaches which are not
> compliant with GPLv2 because they have been released under a license which
> is not in the whitelist of GPLv2.
> http://www.gnu.org/licenses/license-list.html#GPLIncompatibleLicenses
> Check out the incompatible Licenses!
>
> I think it is at the time to make TYPO3 ready for the new "CODINGS" in
> releasing Version TYPO3 6.2.0 LTS Final under GPLv3
>
> Here the thoughts:
>
> We are v2 or later. I guess the question is are we re-licensing all the
> software that is in the distribution package as gpl v2 or later? Or are
> they keeping their respective licenses? If we are re-licensing then I think
> we should re-license the distributions as gpl v3 or later. This would solve
> the incompatibilities.
>
> > I am not sure why we shouldn't. The reason we ask for gplv2 in code is
> > because we haven't relicensed core yet. I don't think there is any
> > legal/technical/spiritual reason why someone would object to making the
> > distribution gpl v3 or later. Technically it's already gpl v3.
> > Beside this it is a matter of fact that we would have already GPLv3 if
> the
> > TYPO3 5 would have worked out. Ok Now we get Neos and Version 6 so why
> not
> > releasing Version 6.2 LTS which breaks anywhay with many other
> conventions
> > and things which were in place before to make it compatible again with
> the
> > modern Free Open Source World incl. Bootstrap usage and other similar
> good
> > code usages released under similar licenses like bootstrap.
>
> ---
>
> Benefits:
>
> A transition from 6.2 to NEOS would be much easier in Terms of Licensing
>
> The use of modern Codings i.e. Bootstrap inside a TYPO3 package would be
> immediately legal with the change to Version 3
>
> Background:
>
> i.e. Bootstrap is released under Apache 2 License which is not compatible
> with GPLv2 because of their Terms in Redistribution:
>
> http://www.apache.org/licenses/LICENSE-2.0.html
>
> *4. Redistribution*. You may reproduce and distribute copies of the Work or
> > Derivative Works thereof in any medium, with or without modifications,
> and
> > in Source or Object form, provided that You meet the following
> conditions:
> >
> >    1. You must give any other recipients of the Work or Derivative Works
> >    a copy of this License; and
> >
> > no bigger problem as the Apache 2 License could be simply added to the
> package
>
>
> >
> >    1. You must cause any modified files to carry prominent notices
> >    stating that You changed the files; and
> >
> > no bigger issue but a bit more code
>
>
> >
> >    1. You must retain, in the Source form of any Derivative Works that
> >    You distribute, all copyright, patent, trademark, and attribution
> notices
> >    from the Source form of the Work, excluding those notices that do not
> >    pertain to any part of the Derivative Works; and
> >
> > ATTENTION!
>
>
> >    1. If the Work includes a "NOTICE" text file as part of its
> >    distribution, then any Derivative Works that You distribute must
> include a
> >    readable copy of the attribution notices contained within such NOTICE
> file,
> >    excluding those notices that do not pertain to any part of the
> Derivative
> >    Works, in at least one of the following places: within a NOTICE text
> file
> >    distributed as part of the Derivative Works; within the Source form or
> >    documentation, if provided along with the Derivative Works; or,
> within a
> >    display generated by the Derivative Works, if and wherever such
> third-party
> >    notices normally appear. The contents of the NOTICE file are for
> >    informational purposes only and do not modify the License. You may
> add Your
> >    own attribution notices within Derivative Works that You distribute,
> >    alongside or as an addendum to the NOTICE text from the Work,
> provided that
> >    such additional attribution notices cannot be construed as modifying
> the
> >    License.
> >
> >
> >    1.
> >
> >
> >    1. You may add Your own copyright statement to Your modifications and
> >    may provide additional or different license terms and conditions for
> use,
> >    reproduction, or distribution of Your modifications, or for any such
> >    Derivative Works as a whole, provided Your use, reproduction, and
> >    distribution of the Work otherwise complies with the conditions
> stated in
> >    this License.
> >
> > Apache 2 License is a free software license, compatible with version 3 of
> > the GNU GPL.
> > Please note that this license is not compatible with GPL version 2,
> > because it has some requirements that are not in the that GPL version.
> > These include certain patent termination and indemnification provisions.
> > The patent termination provision is a good thing, which is why we
> recommend
> > the Apache 2.0 license for substantial programs over other lax permissive
> > licenses.
>
> see here: http://www.gnu.org/licenses/license-list.html
>
> > Please note that GPLv2 is, by itself, not compatible with GPLv3. However,
> > most software released under GPLv2 allows you to use the terms of later
> > versions of the GPL as well. When this is the case, you can use the code
> > under GPLv3 to make the desired combination. To learn more about
> > compatibility between GNU licenses, please see our FAQ<
> http://www.gnu.org/licenses/gpl-faq.html#AllCompatibility>
> > .
>
>
> While GNU recommends the latest Version of GPLv2 for most software it
> recommends to use GPLv3 for Software Packages.
>
> Because TYPO3 needs packages to be easier to use and faster to deploy we
> need IMHO to relicense TYPO3 starting with Veriosn 6.2LTS for GPLv3.
>
> As said Version 2 Extensions will still be able to be used as Version 2
> allows you to continue using your code legally in Version 3! - I repeat:
>
> > However, most software released under GPLv2 allows you to use the terms
> of
> > later versions of the GPL as well. When this is the case, you can use the
> > code under GPLv3 to make the desired combination.
>
>
> So the switch to GPLv3 would be a necessary and it would be a very good
> step for the further and future development of TYPO3.
>
> Andi
> _______________________________________________
> TYPO3-english mailing list
> TYPO3-english at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
>