Re: [TYPO3-english] Locks? What is the concept? and why are they hurting my site?
Am 16.12.2010 18:34, schrieb Morten Kjems: Den 15-12-2010 09:32, Philipp Gampe skrev: that means, TYPO3 uses wrong permissions to create files. You can fix this in Install Tool. Thanks for the hint. I have looked for permission settings but I can't find any. Where do I look? The Temp directory says: typo3temp/temp/ writable Also, what would happen is I disable locks or change the mode to one of the other options, flock or semaphore? Maybe you are seeing an effect of: http://bugs.typo3.org/view.php?id=16749 ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Locks? What is the concept? and why are they hurting my site?
Am 17.12.2010 09:16, schrieb Bjoern Pedersen: Am 16.12.2010 18:34, schrieb Morten Kjems: Den 15-12-2010 09:32, Philipp Gampe skrev: that means, TYPO3 uses wrong permissions to create files. You can fix this in Install Tool. Thanks for the hint. I have looked for permission settings but I can't find any. Where do I look? The Temp directory says: typo3temp/temp/ writable Also, what would happen is I disable locks or change the mode to one of the other options, flock or semaphore? Maybe you are seeing an effect of: http://bugs.typo3.org/view.php?id=16749 Or it's predecessor http://bugs.typo3.org/view.php?id=8980 ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] tesseract + tagpackprovider: how to ignore tags to have show everything ?
I created a new issue and provided a patch: http://forge.typo3.org/issues/11528 That implementation is working for me. On 16 December 2010 18:33, François Suter fsu-li...@cobweb.ch wrote: Hi, I would like to use some special syntax which would mean ignore this criteria but cannot find anything like that in tagpackprovider and expressions documenation. Any suggestions how to solve this ? Indeed, there's nothing like that for now. We could introduce support in tagpackprovider for the keyword \all like in datafilter. Please open a bug report for this. Cheers -- Francois Suter Cobweb Development Sarl - http://www.cobweb.ch ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Extensions potentially violating the GPL
Hi! Kay Strobach wrote: I do not think changing the TER rules solves this Problem. Please, explain your point of view :) -- Dmitry Dulepov TYPO3 coresecurity team member Twitter: http://twitter.com/dmitryd Read more @ http://dmitry-dulepov.com/ ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Extensions potentially violating the GPL
Hi Dimitry, Am 17.12.2010 10:39, schrieb Dmitry Dulepov: Hi! Kay Strobach wrote: I do not think changing the TER rules solves this Problem. Please, explain your point of view :) nothing easier than that: 1) The main Message of TYPO3 is Inspiring people to share 2) Currently most extensions do not contain license information - so they are thought to be GPL (as the author confirmed by registering the license key) - but some are not 3) consistency - the core is GPL so all work depending on the core (e.g. using core libraries) is automatically GPL code. 4) Most people think Ohh Opensource - extensions are opensource too because of GPL - is connected with 1) Using the package_manager and perhaps lateron a hook in extMGM would solve that because the author could include additional components after installation, which do not fit the GPL without publishing them in TER. So the association does not harm any intellectual property by publishing third person work under the GPL. Having the hooks it should be easily possible to show warnings about non GPL code and license information in the TER (and lateron in the extMGM) The other point of view is to ensure the development of extensions after the original authors interest on an extension is gone. So others can contribute to the extension and ensure the further development. This can not be ensured with closed source. Here is how it was done with Joomla JED: http://community.joomla.org/blogs/leadership/636-jed-to-be-gpl-only-by-july-2009.html I'm creating extension to earn money on my own and I'm paid for features, but anyway i mostly publish them in TER (some times with a delay) and most customers allow that after short explanation what opensource is about. But sure there some business relevant parts of projects, which are not public. Best regards Kay ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] List of registers
Hi, François, Unfortunately only a few are documented. This a well-known shortcoming of the current manuals. We would be glad if anyone helped filling this gap actually. Sorry for not being more helpful. Okay, I see now. Anyway, thank you for an answer :) ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Extensions potentially violating the GPL
GPL policy forces company which make huge investiments to not use GPL sw, simply. Best approach is FreeBSD policy: use it whatever you like, but use it. In such a way, usually, a company investing in its work, together with legacy features, usually returns to FreeBSD a lot of improvements, which is better for the same company to put in the FreeBSD mainstream. My example: I'm writing some business extensions, which must be kept private because there is a huge investiment in analisys, which need some improvements on TYPO3 security. So, I'd love to submit these security extensions to TYPO3, but keep business extensions. More, I'd love to publish a ligh compiled version of business extensions, which will be free usable for small business only. In this way I'm encouraged to use TYPO3. If I'm forced to go GPL, I will not use TYPO3. Simply. Regards, Tonino Il 17/12/2010 11:52, Kay Strobach ha scritto: Hi Dimitry, Am 17.12.2010 10:39, schrieb Dmitry Dulepov: Hi! Kay Strobach wrote: I do not think changing the TER rules solves this Problem. Please, explain your point of view :) nothing easier than that: 1) The main Message of TYPO3 is Inspiring people to share 2) Currently most extensions do not contain license information - so they are thought to be GPL (as the author confirmed by registering the license key) - but some are not 3) consistency - the core is GPL so all work depending on the core (e.g. using core libraries) is automatically GPL code. 4) Most people think Ohh Opensource - extensions are opensource too because of GPL - is connected with 1) Using the package_manager and perhaps lateron a hook in extMGM would solve that because the author could include additional components after installation, which do not fit the GPL without publishing them in TER. So the association does not harm any intellectual property by publishing third person work under the GPL. Having the hooks it should be easily possible to show warnings about non GPL code and license information in the TER (and lateron in the extMGM) The other point of view is to ensure the development of extensions after the original authors interest on an extension is gone. So others can contribute to the extension and ensure the further development. This can not be ensured with closed source. Here is how it was done with Joomla JED: http://community.joomla.org/blogs/leadership/636-jed-to-be-gpl-only-by-july-2009.html I'm creating extension to earn money on my own and I'm paid for features, but anyway i mostly publish them in TER (some times with a delay) and most customers allow that after short explanation what opensource is about. But sure there some business relevant parts of projects, which are not public. Best regards Kay ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english -- in...@zioniInterazioni di Antonio Nati http://www.interazioni.it to...@interazioni.it ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
[TYPO3-english] FormHandler: using conditions in Finisher_DB
Hi
I have a contact form on my site, and I wish to insert the userdata to
the tt_address list, but only if:
- the checkbox with the name 'nieuwsflits' was checked
- the e-mail address does not exists yet in the tt_address table
The former works fine, but how do I implement the later?
Thanks in advance!
Regards,
Bart
Typoscript so far:
finishers.3 {
class = Finisher_DB
config {
condition = nieuwsflits
table = tt_address
key = uid
fields {
gender.mapping = aanhef
first_name.mapping = voornaam
last_name.mapping = achternaam
email.mapping = email
phone.mapping = telefoonnummer
mobile.mapping = telmobiel
address.mapping = COA
address.mapping {
1 = TEXT
1.data = GPvar:straatnaam
2 = TEXT
2.data = GPvar:huisnummer
2.noTrimWrap = | | |
}
company.mapping = bedrijf
city.mapping = plaats
zip.mapping = postcode
description = Toegevoegd via contactformulier
module_sys_dmail_html = 1
pid = 154
tstamp.special = sub_tstamp
}
}
}
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Extensions potentially violating the GPL
Hi Tonino, In this way I'm encouraged to use TYPO3. If I'm forced to go GPL, I will not use TYPO3. the core is GPL. That means, that everything which is not usable without the core or uses core API without any alternative is GPLed as far as i understand the GPL. The GPL do not force you to publish all your work. It does say: If you publish/sell this product or a modification the code must be included. So if you decide to not publish an extension nobody has the right to force you to publish this extension - so you have the chance to sell it directly to someone who will than have all the rights which are granted with the GPL. If the product can be used standalone you can use any license you want. Especially for clearifying the situation for users the idea was to make the TER GPL only (what it should be with the current Terms of use.). Than you can use package_manager to show your own license and load your special package from your own server. (So the part which loads your code is definitly GPL). Conclusion: You're forced to go to GPL when product is completly dependent on TYPO3 core or a special extension which is GPL. This is the nature of TYPO3 core GPL licensing. But you can use what ever license you want if your work runs indepently from TYPO3 and uses something like an adapter to be integrated into TYPO3. Best regards Kay ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Extensions potentially violating the GPL
You are GPL, but closed mind. Regards, Tonino Il 17/12/2010 13:32, Kay Strobach ha scritto: Hi Tonino, In this way I'm encouraged to use TYPO3. If I'm forced to go GPL, I will not use TYPO3. the core is GPL. That means, that everything which is not usable without the core or uses core API without any alternative is GPLed as far as i understand the GPL. The GPL do not force you to publish all your work. It does say: If you publish/sell this product or a modification the code must be included. So if you decide to not publish an extension nobody has the right to force you to publish this extension - so you have the chance to sell it directly to someone who will than have all the rights which are granted with the GPL. If the product can be used standalone you can use any license you want. Especially for clearifying the situation for users the idea was to make the TER GPL only (what it should be with the current Terms of use.). Than you can use package_manager to show your own license and load your special package from your own server. (So the part which loads your code is definitly GPL). Conclusion: You're forced to go to GPL when product is completly dependent on TYPO3 core or a special extension which is GPL. This is the nature of TYPO3 core GPL licensing. But you can use what ever license you want if your work runs indepently from TYPO3 and uses something like an adapter to be integrated into TYPO3. Best regards Kay ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english -- in...@zioniInterazioni di Antonio Nati http://www.interazioni.it to...@interazioni.it ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Extensions potentially violating the GPL
Hello Tonino, i do not understand your last post. To make you understand i my opinion collected some information from the official sites (below is the uri/source of the text) Now, browse around, look in the categories, dive into the great manuals and enjoy the beauty of an ordered bazaars unified efforts to bring the most powerful collection of CMS tools to you - for free under the GPL license! http://typo3.org/extensions/what-are-extensions/ By registering an extension key you accept that all content uploaded to TER (TYPO3 Extension Repository) matches these terms: * Published under the GPL license or GPL compatible * You hold the copyright of the code or do not infringe the rights of others (meaning that work from others must be under GPL or GPL compatible already!) Any extensions found to break these terms will be removed without further notice by the webmaster team. http://typo3.org/extensions/extension-keys/ The official extension repository only consists of freely available extensions. http://typo3.org/extensions/repository/ Of course i do understand that programmers need more than grace for live (me too). But the're solutions for divinding Open and Closed Source Parts in an clean and absolute legal way. And that's what is my intention and must be the goal of TER - the legal rules in TER are clear. Additionally there is an interesting blog post @Novell: http://www.novell.com/coolsolutions/feature/1532.html Discussion about GPL Joomla JED: http://community.joomla.org/blogs/leadership/636-jed-to-be-gpl-only-by-july-2009.html Best regards Kay Am 17.12.2010 13:41, schrieb Tonix (Antonio Nati): You are GPL, but closed mind. Regards, Tonino Il 17/12/2010 13:32, Kay Strobach ha scritto: Hi Tonino, In this way I'm encouraged to use TYPO3. If I'm forced to go GPL, I will not use TYPO3. the core is GPL. That means, that everything which is not usable without the core or uses core API without any alternative is GPLed as far as i understand the GPL. The GPL do not force you to publish all your work. It does say: If you publish/sell this product or a modification the code must be included. So if you decide to not publish an extension nobody has the right to force you to publish this extension - so you have the chance to sell it directly to someone who will than have all the rights which are granted with the GPL. If the product can be used standalone you can use any license you want. Especially for clearifying the situation for users the idea was to make the TER GPL only (what it should be with the current Terms of use.). Than you can use package_manager to show your own license and load your special package from your own server. (So the part which loads your code is definitly GPL). Conclusion: You're forced to go to GPL when product is completly dependent on TYPO3 core or a special extension which is GPL. This is the nature of TYPO3 core GPL licensing. But you can use what ever license you want if your work runs indepently from TYPO3 and uses something like an adapter to be integrated into TYPO3. Best regards Kay ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Extensions potentially violating the GPL
Hi Tonino, But there has been a decission about the license a long time ago - perhaps it needs to be discussed - but not in my opinion. All those examples are ok - you're not forced to publish your extensions in TER, so your work will be secret - the discussion is about extensions which are published in the official TER. The publication is a decision of the extension creator - isn't it? Best regards Kay Am 17.12.2010 14:37, schrieb Tonix (Antonio Nati): Kay, if TYPO3 rules are for you like a bible, and cannot be changed, this is for me another announce of TYPO3 decadence. Instead I think rules can be changed, and most people should be encouraged to use TYPO3, despite of how they use it. The most people uses TYPO3, the most TYPO3 will benefit. Look at the FreeBSD licence please. Use me as you want, but use me. GPL means: use me only if your work has not real value for you, because you cannot invest on your work here. Your interest should be TYPO3 growing, and the most interested to a great CMS are those companies which want to invest heavily on business extensions. A lot of REAL professionist could use more TYPO3 and give a huge contribute to TYPO3 API, structures and methodologies. A company which works on its own developments must protect its work. If TYPO3 does not permit that, TYPO3 is not for professionals. Regards, Tonino Il 17/12/2010 14:04, Kay Strobach ha scritto: Hello Tonino, i do not understand your last post. To make you understand i my opinion collected some information from the official sites (below is the uri/source of the text) Now, browse around, look in the categories, dive into the great manuals and enjoy the beauty of an ordered bazaars unified efforts to bring the most powerful collection of CMS tools to you - for free under the GPL license! http://typo3.org/extensions/what-are-extensions/ By registering an extension key you accept that all content uploaded to TER (TYPO3 Extension Repository) matches these terms: * Published under the GPL license or GPL compatible * You hold the copyright of the code or do not infringe the rights of others (meaning that work from others must be under GPL or GPL compatible already!) Any extensions found to break these terms will be removed without further notice by the webmaster team. http://typo3.org/extensions/extension-keys/ The official extension repository only consists of freely available extensions. http://typo3.org/extensions/repository/ Of course i do understand that programmers need more than grace for live (me too). But the're solutions for divinding Open and Closed Source Parts in an clean and absolute legal way. And that's what is my intention and must be the goal of TER - the legal rules in TER are clear. Additionally there is an interesting blog post @Novell: http://www.novell.com/coolsolutions/feature/1532.html Discussion about GPL Joomla JED: http://community.joomla.org/blogs/leadership/636-jed-to-be-gpl-only-by-july-2009.html Best regards Kay Am 17.12.2010 13:41, schrieb Tonix (Antonio Nati): You are GPL, but closed mind. Regards, Tonino Il 17/12/2010 13:32, Kay Strobach ha scritto: Hi Tonino, In this way I'm encouraged to use TYPO3. If I'm forced to go GPL, I will not use TYPO3. the core is GPL. That means, that everything which is not usable without the core or uses core API without any alternative is GPLed as far as i understand the GPL. The GPL do not force you to publish all your work. It does say: If you publish/sell this product or a modification the code must be included. So if you decide to not publish an extension nobody has the right to force you to publish this extension - so you have the chance to sell it directly to someone who will than have all the rights which are granted with the GPL. If the product can be used standalone you can use any license you want. Especially for clearifying the situation for users the idea was to make the TER GPL only (what it should be with the current Terms of use.). Than you can use package_manager to show your own license and load your special package from your own server. (So the part which loads your code is definitly GPL). Conclusion: You're forced to go to GPL when product is completly dependent on TYPO3 core or a special extension which is GPL. This is the nature of TYPO3 core GPL licensing. But you can use what ever license you want if your work runs indepently from TYPO3 and uses something like an adapter to be integrated into TYPO3. Best regards Kay ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Extensions potentially violating the GPL
Tonix, let me say that you seem to have your bible as well: there are different business models and your point of view applies to one of them. What is Typo3 as a whole if not an enormous investment? The problem here is that Typo3 should not be moved by corporate investments but by developer investments (by developer communities, to be more precise). And Typo3 and its extensions should be shared because that would increase the value of Typo3 as a product and all its developers as professionals. And to expose only the work of a group of them. At least in the intention of who founded Typo3. To be closed mind in my opinion is not to recognize that exist other ways to look at the same things and most of all have their dignity. BTW to me the meaning of publishing extensions on TER that are not GPL does not lead to protect customer investments, but only to give visibility to some work produced by someone. So what is really protected is the work made by the developer, not by the customer. But this is only a way to look at how to protect developers. The demonstration of this is that Typo3 had the ability to become one of the most used CMS in the world and a lot of people is making a living out of it. I too prefer FreeBSD to GPL because of how I works or how the business environment around me leads me to work. But I would not say to anyone that is closed mind because he either thinks different of me or has different needs. Il 17/12/2010 14.37, Tonix (Antonio Nati) ha scritto: Kay, if TYPO3 rules are for you like a bible, and cannot be changed, this is for me another announce of TYPO3 decadence. Instead I think rules can be changed, and most people should be encouraged to use TYPO3, despite of how they use it. The most people uses TYPO3, the most TYPO3 will benefit. Look at the FreeBSD licence please. Use me as you want, but use me. GPL means: use me only if your work has not real value for you, because you cannot invest on your work here. Your interest should be TYPO3 growing, and the most interested to a great CMS are those companies which want to invest heavily on business extensions. A lot of REAL professionist could use more TYPO3 and give a huge contribute to TYPO3 API, structures and methodologies. A company which works on its own developments must protect its work. If TYPO3 does not permit that, TYPO3 is not for professionals. Regards, Tonino Il 17/12/2010 14:04, Kay Strobach ha scritto: Hello Tonino, i do not understand your last post. To make you understand i my opinion collected some information from the official sites (below is the uri/source of the text) Now, browse around, look in the categories, dive into the great manuals and enjoy the beauty of an ordered bazaars unified efforts to bring the most powerful collection of CMS tools to you - for free under the GPL license! http://typo3.org/extensions/what-are-extensions/ By registering an extension key you accept that all content uploaded to TER (TYPO3 Extension Repository) matches these terms: * Published under the GPL license or GPL compatible * You hold the copyright of the code or do not infringe the rights of others (meaning that work from others must be under GPL or GPL compatible already!) Any extensions found to break these terms will be removed without further notice by the webmaster team. http://typo3.org/extensions/extension-keys/ The official extension repository only consists of freely available extensions. http://typo3.org/extensions/repository/ Of course i do understand that programmers need more than grace for live (me too). But the're solutions for divinding Open and Closed Source Parts in an clean and absolute legal way. And that's what is my intention and must be the goal of TER - the legal rules in TER are clear. Additionally there is an interesting blog post @Novell: http://www.novell.com/coolsolutions/feature/1532.html Discussion about GPL Joomla JED: http://community.joomla.org/blogs/leadership/636-jed-to-be-gpl-only-by-july-2009.html Best regards Kay Am 17.12.2010 13:41, schrieb Tonix (Antonio Nati): You are GPL, but closed mind. Regards, Tonino Il 17/12/2010 13:32, Kay Strobach ha scritto: Hi Tonino, In this way I'm encouraged to use TYPO3. If I'm forced to go GPL, I will not use TYPO3. the core is GPL. That means, that everything which is not usable without the core or uses core API without any alternative is GPLed as far as i understand the GPL. The GPL do not force you to publish all your work. It does say: If you publish/sell this product or a modification the code must be included. So if you decide to not publish an extension nobody has the right to force you to publish this extension - so you have the chance to sell it directly to someone who will than have all the rights which are granted with the GPL. If the product can be used standalone you can use any license you want.
Re: [TYPO3-english] Extensions potentially violating the GPL
A company which works on its own developments must protect its work. If TYPO3 does not permit that, TYPO3 is not for professionals. You still miss the point completely. And there is bad news for you: Since the TYPO3 license forces you to sell your extensions with a compatible license, all your clients already can publish the stuff you did for them without having to ask you for permission. BUT: GPL doesn't force anybody to publish anything, if people don't want to give something back for free, although they got the TYPO3 core for free, which is worth hundreds of thousands of working hours. So you and your clients can keep your stuff private as long as you like and charge other people as much as you like for it. And if the amount you charged was high enough, most likely the clients will not publish the stuff you sold them as well, although the GPL would allow them to do so. BUT: Since the current TYPO3 core is bound to the GPL license, you can not simply switch to another one, because this is exactly what the GPL license does NOT allow. Everybody who contributed stuff for the core did so while accepting the terms of the GPL, so publishing the core with another license would be possible ONLY with the permission of each and everybody who contributed, which is not very realstic. But even IF everybody agreed, the GPL would make sure, that the current GPLed version of the core would STILL be available together with the version using the other license. But you should not be afraid too much, since according to some official T3A sources the amount of money made by TYPO3 developers and agencies all over the world is a few hundred million dollars per year. So I guess there will be something left for you as well ;-) Have a nice weekend Joey -- Wenn man keine Ahnung hat: Einfach mal Fresse halten! (If you have no clues: simply shut your gob sometimes!) Dieter Nuhr, German comedian Xing: http://contact.cybercraft.de Twitter: http://twitter.com/bunnyfield TYPO3 cookbook (2nd edition): http://www.typo3experts.com ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Extensions potentially violating the GPL
Il 17/12/2010 15:38, JoH asenau ha scritto: A company which works on its own developments must protect its work. If TYPO3 does not permit that, TYPO3 is not for professionals. You still miss the point completely. And there is bad news for you: Since the TYPO3 license forces you to sell your extensions with a compatible license, all your clients already can publish the stuff you did for them without having to ask you for permission. Oh, really? I do not see anything forcing me to sell extensions that way. The most you can pretend is I cannot load those extensions in TER. If that makes you happy, continue without problems, I will survive. Regards, Tonino BUT: GPL doesn't force anybody to publish anything, if people don't want to give something back for free, although they got the TYPO3 core for free, which is worth hundreds of thousands of working hours. So you and your clients can keep your stuff private as long as you like and charge other people as much as you like for it. And if the amount you charged was high enough, most likely the clients will not publish the stuff you sold them as well, although the GPL would allow them to do so. BUT: Since the current TYPO3 core is bound to the GPL license, you can not simply switch to another one, because this is exactly what the GPL license does NOT allow. Everybody who contributed stuff for the core did so while accepting the terms of the GPL, so publishing the core with another license would be possible ONLY with the permission of each and everybody who contributed, which is not very realstic. But even IF everybody agreed, the GPL would make sure, that the current GPLed version of the core would STILL be available together with the version using the other license. But you should not be afraid too much, since according to some official T3A sources the amount of money made by TYPO3 developers and agencies all over the world is a few hundred million dollars per year. So I guess there will be something left for you as well ;-) Have a nice weekend Joey -- in...@zioniInterazioni di Antonio Nati http://www.interazioni.it to...@interazioni.it ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Extensions potentially violating the GPL
Il 17/12/2010 15:26, Ivano Luberti ha scritto: Tonix, let me say that you seem to have your bible as well: there are different business models and your point of view applies to one of them. Ivano, I'm saying all models should be accepted and live together. You are saying only your model must be accepted. Regards, Tonino -- in...@zioniInterazioni di Antonio Nati http://www.interazioni.it to...@interazioni.it ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Extensions potentially violating the GPL
Am 17.12.2010 16:16, schrieb Tonix (Antonio Nati): Oh, really? I do not see anything forcing me to sell extensions that way. The most you can pretend is I cannot load those extensions in TER. it is the GPL license which forces you to put anything under GPL (or compatible) license. Any extension which depends on the core *must* be under GPL, there is *no* other way. This still means that you can sell the extension, can keep it yourself and so on. If you sell/give away the extension to somebody else and you don't provide it as GPL, you can be sued IANAL (!). Georg ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Extensions potentially violating the GPL
Hi, a small contribution... 1) It shouldn't go the way it goes with Joomla. There you have to buy (the best) extensions. Am I right? 2) There are people making not that much money with TYPO3, and who are poor programmers. They contribute to making TYPO3 a popular system by simply using it for their (small) customers. Good quality should not only be available to those who pay much money. So, TYPO3 must be there for the little customers too. 3) It is understandable that different programmers want to protect their software differently, for several reasons. Do we agree on that? If so, perhaps there should be a way for contributors to the TER to choose another license. Perhaps from some of the Creative Commons licenses? For the already build extensions that are not maintained, the author can be asked what he/she wants? And if he/she doesn't respond, the TYPO3 organisation can take the appropriate action. Changing the license or keeping it to GPL... whatever. Hope it adds to the discussion. Vincent ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Extensions potentially violating the GPL
Hi, On Fri, 17 Dec 2010 16:39:57 +0100, Vincent Mans wrote: For the already build extensions that are not maintained, the author can be asked what he/she wants? And if he/she doesn't respond, the TYPO3 organisation can take the appropriate action. Changing the license or keeping it to GPL... whatever. You CAN *NOT* change GPL unless you have permission my all contributors. Best regards Phil ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Extensions potentially violating the GPL
And there is bad news for you: Since the TYPO3 license forces you to sell your extensions with a compatible license, all your clients already can publish the stuff you did for them without having to ask you for permission. Oh, really? I do not see anything forcing me to sell extensions that way. The most you can pretend is I cannot load those extensions in TER. If that makes you happy, continue without problems, I will survive. Well - maybe you should have read the GPL completely before starting to sell extensions to your clients. You may believe it or not, but the fact that the TYPO3 Core is GPLed automatically makes any of your extensions using the TYPO3 core API GPLed by definition as well. Even if you didn't explicitly tell your client or gave it another license, which is just a violation of the GPL that might cause legal actions taken against you, any of your clients has got the privileges that the GPL assures him, which are: + to freely modify the code, + to publish it for a certain fee or + to publish it for free + to build other pieces of software based on it with the only restriction for your clients, that any of the above actions includes the GPL as the license. This means that any of your clients could even reserve an extension key in the TER, upload your extension and make it available to the community for free. Of course nobody can force them to do so, but the GPL would grant them these privileges if they wanted to. Cheers Joey -- Wenn man keine Ahnung hat: Einfach mal Fresse halten! (If you have no clues: simply shut your gob sometimes!) Dieter Nuhr, German comedian Xing: http://contact.cybercraft.de Twitter: http://twitter.com/bunnyfield TYPO3 cookbook (2nd edition): http://www.typo3experts.com ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Extensions potentially violating the GPL
What I'm saying is that GPL is part of TYPO3 from the beginning and if you don't wanted to use GPL you should have chosen another CMS. Once you choose a software you also have chosen its licence. Haven't you? For what I have understood it's you that are asking TYPO3 to change to another licence. Il 17/12/2010 16.19, Tonix (Antonio Nati) ha scritto: Il 17/12/2010 15:26, Ivano Luberti ha scritto: Tonix, let me say that you seem to have your bible as well: there are different business models and your point of view applies to one of them. Ivano, I'm saying all models should be accepted and live together. You are saying only your model must be accepted. Regards, Tonino -- == dott. Ivano Mario Luberti Archimede Informatica societa' cooperativa a r. l. Sede Operativa Via Gereschi 36 - 56126- Pisa tel.: +39-050- 580959 tel/fax: +39-050-9711344 web: www.archicoop.it == ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Extensions potentially violating the GPL
Am 17.12.10 17:28, schrieb JoH asenau: This means that any of your clients could even reserve an extension key in the TER, upload your extension and make it available to the community for free. Of course nobody can force them to do so, but the GPL would grant them these privileges if they wanted to. Thats the way the christmas cookie crumbles! Merry X-Mas and a leaky new Year everyone! Yours truly, Reverend Neverend! ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Extensions potentially violating the GPL
Hey Joey Well - maybe you should have read the GPL completely before starting to sell extensions to your clients. You may believe it or not, but the fact that the TYPO3 Core is GPLed automatically makes any of your extensions using the TYPO3 core API GPLed by definition as well. Even if you didn't explicitly tell your client or gave it another license, which is just a violation of the GPL that might cause legal actions taken against you, any of your clients has got the privileges that the GPL assures him, which are: + to freely modify the code, + to publish it for a certain fee or + to publish it for free + to build other pieces of software based on it with the only restriction for your clients, that any of the above actions includes the GPL as the license. This means that any of your clients could even reserve an extension key in the TER, upload your extension and make it available to the community for free. Of course nobody can force them to do so, but the GPL would grant them these privileges if they wanted to. Cheers Joey +1 therefore i added the paragraph about postloading non GPL parts additionally of extensions (f.e. yaml, etc.) after installing the pure GPL part to the wiki (i'll prefer complete GPL - in this case - but sometimes no GPL aquivalent is available). http://wiki.typo3.org/Overview_Extension_manuals#Non-GPL_compatible_extensions_.28to_be_removed_from_TER.29 Best regards Kay ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Extensions potentially violating the GPL
Well, if you're really concerning about your proprietary extension,
there is a trick. First, find all TYPO3 calls/classes in your extension.
Then create a 'wrapper' library, say (just an example)
function MYSTUFF::makeInstance ($parameters ...)
{
return t3lib_div::makeInstance($parameters);
}
.
'Release' this library under LGPL v2.1, which is GPL compatible and
permits linking with non-free modules
(http://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses)
Use it with your extension :)
Best wishes
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] List of registers
For anyone, who will search for same topic, I've made a research by simple
search of '$GLOBALS['TSFE']-register' ($TSFE-register gave 0 results) in
content of all PHP files in TYPO3 4.4. Here is a list with some my
explanations:
class.tx_cssstyled_content_pi1.php
function render_uploads($content,$conf) - Rendering the Filelinks type
content element, called from TypoScript (tt_content.uploads.20):
$GLOBALS['TSFE']-register['ICON_REL_PATH'] - keeps relative path to file +
filename
$GLOBALS['TSFE']-register['filename'] - self-explainable
$GLOBALS['TSFE']-register['path'] - self-explainable
$GLOBALS['TSFE']-register['fileSize'] - self-explainable
$GLOBALS['TSFE']-register['fileExtension'] - self-explainable
$GLOBALS['TSFE']-register['description'] - description for current file
from 'imagecaption' field
$GLOBALS['TSFE']-register['linkedIcon'] - not sure about that, but I think
is is bool value, defining, should file icon be linked or not
$GLOBALS['TSFE']-register['linkedLabel'] - same as above, but for label
function render_textpic($content, $conf) - Rendering the IMGTEXT content
element, called from TypoScript (tt_content.textpic.20)
$GLOBALS['TSFE']-register['imageCount'] - count of all image in block
$GLOBALS['TSFE']-register['renderGlobalCaption'] - bool value, which
defines, shoul a global caption be rendered below image block
$GLOBALS['TSFE']-register['IMAGE_NUM'] - number of current image in set
(DEPRECATED)
$GLOBALS['TSFE']-register['IMAGE_NUM_CURRENT'] - number of current image in
set (not deprecated :))
$GLOBALS['TSFE']-register['ORIG_FILENAME'] - path to the image + image name
$GLOBALS['TSFE']-register['imagewidth'] - self-explainable
$GLOBALS['TSFE']-register['imagespace'] - self-explainable
$GLOBALS['TSFE']-register['imageheight'] - self-explainable
$GLOBALS['TSFE']-register['rowwidth'] - width of whole block of images
$GLOBALS['TSFE']-register['rowWidthPlusTextMargin'] - same, as above +
margin to the text
$GLOBALS['TSFE']-register['columnwidth'] - maximum possible width of image
block + spaces at left and right side of block
$GLOBALS['TSFE']-register['totalwidth'] - not sure, but I guess it is same
as $GLOBALS['TSFE']-register['rowwidth']
class.tslib_content.php
function IMGTEXT($conf)
$GLOBALS['TSFE']-register['IMAGE_NUM']
$GLOBALS['TSFE']-register['IMAGE_NUM_CURRENT']
function HMENU($conf)
$GLOBALS['TSFE']-register['count_HMENU'] - current number of a generated
HMENU on a website
$GLOBALS['TSFE']-register['count_HMENU_MENUOBJ'] - number of current menu
item for current HMENU object
function SEARCHRESULT($conf)
$GLOBALS['TSFE']-register['SWORD_PARAMS'] - search words
function TEMPLATE($conf)
$GLOBALS['TSFE']-register['SUBPART_'.$theKey] - contains html code of
subpart, defined by $theKey
public function SWFOBJECT($conf)
$GLOBALS['TSFE']-register['MMSWFID'] - not sure, what it used for, but it
holds: uniqid('mmswf');
public function QTOBJECT($conf)
$GLOBALS['TSFE']-register['MMQTID'] - uniqid('mmqt');
function lastChanged($tstamp) - Sets the SYS_LASTCHANGED timestamp
$GLOBALS['TSFE']-register['SYS_LASTCHANGED'] - timestamp of page (or
content on current page) last modification
function splitObj($value, $conf) - Implements the split property of
stdWrap; Splits a string based on a token (given in TypoScript properties),
sets the current value to each part and then renders a content object
pointer to by a number.
$GLOBALS['TSFE']-register['SPLIT_COUNT'] - current number of item in split
class.tslib_menu.php
function makeMenu() - Creates the menu in the internal variables, ready for
output.
$GLOBALS['TSFE']-register['count_menuItems'] - number of all items in
current menu
function subMenu($uid, $objSuffix='') - Creates a submenu level to the
current level - if configured for.
$GLOBALS['TSFE']-register['count_menuItems'] - as I understood this
register holds number of items not for the whole menu, but for current menu
level
function writeMenu() - Traverses the -result array of menu items
configuration (made by -generate()) and renders each item.
$GLOBALS['TSFE']-register['count_HMENU_MENUOBJ'] - number of current menu
item for current HMENU object
$GLOBALS['TSFE']-register['count_MENUOBJ'] - number of current menu item
for ALL HMENU objects on a page
Hope, that can help for someone after me :)
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Extensions potentially violating the GPL
Hello list, i contacted the association to get a clear legal statement This is the interesting part of the answere: Peter Proell: A quick and straight forward statement: Everything is said and written down. In GPL and when uploading an extension to TER. A longer statement: As I learned from the thread by just browsing it, it seems not as simple. Actually I have to read through the thread in dept, will forward this to the board and steering committee if needed and will come back to you after that. The next board conference will be on Jan, 20th. There won't be a statement before. Thanks for being part of TYPO3. Best regards Kay ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Extensions potentially violating the GPL
Il 17/12/2010 16:27, Georg Ringer ha scritto: Am 17.12.2010 16:16, schrieb Tonix (Antonio Nati): Oh, really? I do not see anything forcing me to sell extensions that way. The most you can pretend is I cannot load those extensions in TER. it is the GPL license which forces you to put anything under GPL (or compatible) license. Any extension which depends on the core *must* be under GPL, there is *no* other way. This is your idea of GPL. I'm writing PHP libraries which are indipendent of typo3, and my extensions call both typo3 and indipendent libraries. So, extensions can be forced to be GPL, but my external libraries not, because they are called from extensions and do not rely at all on any TYPO3 feature and live outside typo3. I can do whatever I want of these libraries, despite you GPL ideas. I could not imagine how much people wants to limit freedom in name of GPL! My thread stops here. Regards, Tonino This still means that you can sell the extension, can keep it yourself and so on. If you sell/give away the extension to somebody else and you don't provide it as GPL, you can be sued IANAL (!). Georg ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english -- in...@zioniInterazioni di Antonio Nati http://www.interazioni.it to...@interazioni.it ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Extensions potentially violating the GPL
Hi, On Fri, Dec 17, 2010 at 11:06 AM, Tonix (Antonio Nati) to...@interazioni.it wrote: Il 17/12/2010 16:27, Georg Ringer ha scritto: Am 17.12.2010 16:16, schrieb Tonix (Antonio Nati): Oh, really? I do not see anything forcing me to sell extensions that way. The most you can pretend is I cannot load those extensions in TER. it is the GPL license which forces you to put anything under GPL (or compatible) license. Any extension which depends on the core *must* be under GPL, there is *no* other way. This is your idea of GPL. I'm writing PHP libraries which are indipendent of typo3, and my extensions call both typo3 and indipendent libraries. So, extensions can be forced to be GPL, but my external libraries not, because they are called from extensions and do not rely at all on any TYPO3 feature and live outside typo3. I can do whatever I want of these libraries, despite you GPL ideas. I could not imagine how much people wants to limit freedom in name of GPL! Well, first of all this is precisely what what the LGPL is for. Read back in the thread for a very clear explanation. Secondly, the GPL does the things described by others in this thread *by desgin*. It's foolish to debate whether or not a TYPO3 extension should be licensed under the GPL because, being entirely dependent on a piece of GPL software to merely operate, it can't possibly *not* be GPL licensed. It's amusing that you contort what you've read in this thread to say that people wish to limit freedom in the name of the GPL. The only freedom that's limited is that of software authors, in that if they release their work under the GPL, they *must* abide by certain conditions. Even this is not a severe limitation in that developers remain free to write code or use frameworks with different licenses (this does not include writing wholly closed components for GPL frameworks...) Software *users* have gained inestimably from the GPL, and if you're fighting against the GPL, you're fighting the people who use your software. Not smart. -- Christopher Torgalson http://www.typo3apprentice.com/ ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Extensions potentially violating the GPL
http://www.gnu.org/licenses/gpl-faq.html Regards Kay ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
