[TYPO3-50-general] FLOW3CGL license header/annotation check
Malte Jansen
mail at maltejansen.de
Thu Jan 15 17:00:14 CET 2009
Hi Karsten,
Karsten Dambekalns schrieb:
> Hi Malte et al.
>
> First things first: there is no need to have everything FLOW3 being
> released as LGPL. Your packages can be GPL as well.
Ok, I was sure about it.
>
> Thus, after looking at r1743 (Adjustment of Check for Copyright.
> Checking for new copyright header) I think the checks need to allow for
> more flexible checking.
Just write you comments to the FLOW3 header:
-----
This script belongs to the FLOW3 framework. *
It is free software; you can redistribute it and/or modify it under *
the terms of the GNU Lesser General Public License as published by the *
Free Software Foundation, either version 3 of the License, or (at your *
option) any later version. *
This script is distributed in the hope that it will be useful, but *
WITHOUT ANY WARRANTY; without even the implied warranty of MERCHAN- *
TABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser *
General Public License for more details. *
You should have received a copy of the GNU Lesser General Public *
License along with the script. *
If not, see http://www.gnu.org/licenses/lgpl.html *
The TYPO3 project - inspiring people to share! *
----
Do we realy need this long license header? Isn't it just enough if you
write something like:
----
This script belongs to the ###longpackagename###. *
It is free software; you can redistribute it and/or modify it under *
the terms of the license defined in @license-tag at the File-DocComment
beneath this comment. *
This script is distributed in the hope that it will be useful, but *
WITHOUT ANY WARRANTY; without even the implied warranty of MERCHAN- *
TABILITY or FITNESS FOR A PARTICULAR PURPOSE. See @license-tag for more
details. *
The TYPO3 project - inspiring people to share! *
---
> * The header comment only reads "This script belongs to the FLOW3
> framework." for the FLOW3 package itself. Other packages differ in that
> line.
"This script belongs to the ###LONGPACKAGENAME###."
Should be possible to read from the MyPackage/Meta/Package.xml.
Is there model/class of the package information, from which you can just
get/import these informations?
> * The license may be GPL as well, probably even other (L)GPL compatible
> licenses, or (for things being developed commercially) even something
> completely different.
There should be some page were, the licenses are collected...
Just for completition:
http://www.fsf.org/licensing/licenses/index_html
> * The @license annotation is a must, though, and should be consistent
> within a package.
Ok
> Maybe the expected license and package key can be given to the tool, so
> it can adjust the checks based on that.
Should be possible. See my question above.
Cheers,
Malte
More information about the TYPO3-project-5_0-general
mailing list