Re: [Wicket-user] License for CMS (components)
can they really do that?I think you can make a close source project on top of it. But shouldn't the wicket part, that is written by all of us, still be open? johan On 9/26/06, Martijn Dashorst [EMAIL PROTECTED] wrote: It is true that a company can take the source code and make it closedand sell it with a new label when using Apache license. Personally Idon't mind and there are a lot of people that don't mind either.The problem with taking the ASL product, rebrand it and market it is that the product will always be behind what the free version provides,as long as the community is active and participating.I don't consider GPL or LGPL to be evil, they are just not my cup of tea.Martijn On 9/26/06, Che Schneider [EMAIL PROTECTED] wrote: Hi Martijn, Well said - I did not think about that. And agreed, you might very well run into that problem. I admit that I have not had a thorough look at the Apache license but only 'read over it' and found it to be too 'open' for my liking: if you use an Apache-d software, you can keep the whole source secret, you can have it all open source, whatever. :) On the other hand, is it not true that Apache 2 is compatible with GPL? *mental note: read Apache and Apache 2 again* // Che -Original Message- From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED]] On Behalf Of Martijn Dashorst Sent: Tuesday, September 26, 2006 2:32 PM To: wicket-user@lists.sourceforge.net Subject: Re: [Wicket-user] License for CMS (components) I'm very biased against LGPL. The letter of the license is not applicable for Java use, and LGPL is strongly at odds with Apache license. If at some time we would like to adopt such components when we arrive at Apache, then this will prohibit reusing any code from this project. I'm in favor of Apache 2, since that is what most Wicket projects are based on. I would use a license that is at least compatible with Apache. Martijn On 9/26/06, Che Schneider [EMAIL PROTECTED] wrote: Hi, My vote goes to LGPL: not as restrictive as GPL but preserves the gist of it. :) // Che -Original Message-From: [EMAIL PROTECTED][mailto:[EMAIL PROTECTED]] On BehalfOf Ted Roeloffzen Sent: Tuesday, September 26, 2006 2:13 PMTo: wicket-userSubject: [Wicket-user] License for CMS (components) Hello all, We are going to create a Wicket CMS and/or CMS Components,but we are not sure under which license to do this. Whichlicense would you prefer? BSD, Apache, (L)GPL or another one? greets, Ted__DISCLAIMER: This e-mail message is intended for the addressee(s) or authorized recipient only. If you are not theaddressee, or an authorized recipient, you are specificallyadvised that any use, distribution, publication, copying or repetition of this information is prohibited. If you havereceived this information in error, please notify usimmediately (+31 (0)20 50 25 800) and destroy this message.__DISCLAIMER: This e-mail message is intended for theaddressee(s) or authorized recipient only. If you are not the addressee, or an authorized recipient, you are specificallyadvised that any use, distribution, publication, copying orrepetition of this information is prohibited. If you have received this information in error, please notify usimmediately (+31 (0)20 50 25 800) and destroy this message. __ DISCLAIMER: This e-mail message is intended for the addressee(s) or authorized recipient only. If you are not the addressee, or an authorized recipient, you are specifically advised that any use, distribution, publication, copying or repetition of this information is prohibited. If you have received this information in error, please notify us immediately (+31 (0)20 50 25 800) and destroy this message. -- --- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforge CID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- a href="" href="http://www.thebeststuffintheworld.com/vote_for/wicket"> http://www.thebeststuffintheworld.com/vote_for/wicketVote/a for a href="" href="http://www.thebeststuffintheworld.com/stuff/wicket">http://www.thebeststuffintheworld.com/stuff/wicket Wicket/a at the a href="" href="http://www.thebeststuffintheworld.com/">http://www.thebeststuffintheworld.com/Best Stuff in the World!/a ---
Re: [Wicket-user] License for CMS (components)
Johan Compagner wrote: can they really do that? I think you can make a close source project on top of it. But shouldn't the wicket part, that is written by all of us, still be open? Someone can take ASL licensed code, and make a closed source project from it. They cannot use the Wicket name, but they can say based upon Wicket. They can't stop the Wicket code from being distributed, though. And they presumably can't stop the Wicket committers from being those who know the code the best. Upayavira On 9/26/06, *Martijn Dashorst* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: It is true that a company can take the source code and make it closed and sell it with a new label when using Apache license. Personally I don't mind and there are a lot of people that don't mind either. The problem with taking the ASL product, rebrand it and market it is that the product will always be behind what the free version provides, as long as the community is active and participating. I don't consider GPL or LGPL to be evil, they are just not my cup of tea. Martijn On 9/26/06, Che Schneider [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi Martijn, Well said - I did not think about that. And agreed, you might very well run into that problem. I admit that I have not had a thorough look at the Apache license but only 'read over it' and found it to be too 'open' for my liking: if you use an Apache-d software, you can keep the whole source secret, you can have it all open source, whatever. :) On the other hand, is it not true that Apache 2 is compatible with GPL? *mental note: read Apache and Apache 2 again* // Che -Original Message- From: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]] On Behalf Of Martijn Dashorst Sent: Tuesday, September 26, 2006 2:32 PM To: wicket-user@lists.sourceforge.net mailto:wicket-user@lists.sourceforge.net Subject: Re: [Wicket-user] License for CMS (components) I'm very biased against LGPL. The letter of the license is not applicable for Java use, and LGPL is strongly at odds with Apache license. If at some time we would like to adopt such components when we arrive at Apache, then this will prohibit reusing any code from this project. I'm in favor of Apache 2, since that is what most Wicket projects are based on. I would use a license that is at least compatible with Apache. Martijn On 9/26/06, Che Schneider [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi, My vote goes to LGPL: not as restrictive as GPL but preserves the gist of it. :) // Che -Original Message- From: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]] On Behalf Of Ted Roeloffzen Sent: Tuesday, September 26, 2006 2:13 PM To: wicket-user Subject: [Wicket-user] License for CMS (components) Hello all, We are going to create a Wicket CMS and/or CMS Components, but we are not sure under which license to do this. Which license would you prefer? BSD, Apache, (L)GPL or another one? greets, Ted __ DISCLAIMER: This e-mail message is intended for the addressee(s) or authorized recipient only. If you are not the addressee, or an authorized recipient, you are specifically advised that any use, distribution, publication, copying or repetition of this information is prohibited. If you have received this information in error, please notify us immediately (+31 (0)20 50 25 800) and destroy this message.__ DISCLAIMER: This e-mail message is intended for the addressee(s) or authorized recipient only. If you are not the addressee, or an authorized recipient, you are specifically advised that any use, distribution, publication, copying or repetition of this information is prohibited. If you have received this information in error, please notify us immediately (+31 (0)20 50 25 800) and destroy this message. __ DISCLAIMER: This e-mail message is intended for the addressee(s) or authorized recipient only. If you are not the addressee, or an authorized recipient, you
Re: [Wicket-user] License for CMS (components)
Johan, It would still remain open. Think of the closed-source version as a branch of the open-source software that is maintained by that un-named company. Of course, they'd have to deal with the headache of keeping their own branch updated with the latest patches and such (or just go their own route and now worry about the original OS software's changes). If I where such a company, I think I'd rather try to build a business model around the OS software than trying to constantly keep my own branch of an OS project up to date with changes. On Tue, 2006-10-03 at 23:12 +0200, Johan Compagner wrote: can they really do that? I think you can make a close source project on top of it. But shouldn't the wicket part, that is written by all of us, still be open? johan On 9/26/06, Martijn Dashorst [EMAIL PROTECTED] wrote: It is true that a company can take the source code and make it closed and sell it with a new label when using Apache license. Personally I don't mind and there are a lot of people that don't mind either. The problem with taking the ASL product, rebrand it and market it is that the product will always be behind what the free version provides, as long as the community is active and participating. I don't consider GPL or LGPL to be evil, they are just not my cup of tea. Martijn On 9/26/06, Che Schneider [EMAIL PROTECTED] wrote: Hi Martijn, Well said - I did not think about that. And agreed, you might very well run into that problem. I admit that I have not had a thorough look at the Apache license but only 'read over it' and found it to be too 'open' for my liking: if you use an Apache-d software, you can keep the whole source secret, you can have it all open source, whatever. :) On the other hand, is it not true that Apache 2 is compatible with GPL? *mental note: read Apache and Apache 2 again* // Che -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Martijn Dashorst Sent: Tuesday, September 26, 2006 2:32 PM To: wicket-user@lists.sourceforge.net Subject: Re: [Wicket-user] License for CMS (components) I'm very biased against LGPL. The letter of the license is not applicable for Java use, and LGPL is strongly at odds with Apache license. If at some time we would like to adopt such components when we arrive at Apache, then this will prohibit reusing any code from this project. I'm in favor of Apache 2, since that is what most Wicket projects are based on. I would use a license that is at least compatible with Apache. Martijn On 9/26/06, Che Schneider [EMAIL PROTECTED] wrote: Hi, My vote goes to LGPL: not as restrictive as GPL but preserves the gist of it. :) // Che -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Ted Roeloffzen Sent: Tuesday, September 26, 2006 2:13 PM To: wicket-user Subject: [Wicket-user] License for CMS (components) Hello all, We are going to create a Wicket CMS and/or CMS Components, but we are not sure under which license to do this. Which license would you prefer? BSD, Apache, (L)GPL or another one? greets, Ted __ DISCLAIMER: This e-mail message is intended for the addressee(s) or authorized recipient only. If you are not the addressee, or an authorized recipient, you are specifically advised that any use, distribution, publication, copying or repetition of this information is prohibited. If you have received this information in error, please notify us immediately (+31 (0)20 50 25 800) and destroy this message.__ DISCLAIMER: This e-mail message is intended for the addressee(s) or authorized recipient only. If you are not the addressee, or an authorized recipient, you are specifically advised that any use, distribution, publication, copying or repetition of this information is prohibited. If you have received this information in error, please notify us immediately (+31 (0)20 50 25 800) and destroy
Re: [Wicket-user] License for CMS (components)
We want to keep it open source, but there are so many different licenses to choose from.TedOn 10/3/06, Johan Compagner [EMAIL PROTECTED] wrote:can they really do that?I think you can make a close source project on top of it. But shouldn't the wicket part, that is written by all of us, still be open? johan On 9/26/06, Martijn Dashorst [EMAIL PROTECTED] wrote: It is true that a company can take the source code and make it closedand sell it with a new label when using Apache license. Personally Idon't mind and there are a lot of people that don't mind either.The problem with taking the ASL product, rebrand it and market it is that the product will always be behind what the free version provides,as long as the community is active and participating.I don't consider GPL or LGPL to be evil, they are just not my cup of tea. Martijn On 9/26/06, Che Schneider [EMAIL PROTECTED] wrote: Hi Martijn, Well said - I did not think about that. And agreed, you might very well run into that problem. I admit that I have not had a thorough look at the Apache license but only 'read over it' and found it to be too 'open' for my liking: if you use an Apache-d software, you can keep the whole source secret, you can have it all open source, whatever. :) On the other hand, is it not true that Apache 2 is compatible with GPL? *mental note: read Apache and Apache 2 again* // Che -Original Message- From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED]] On Behalf Of Martijn Dashorst Sent: Tuesday, September 26, 2006 2:32 PM To: wicket-user@lists.sourceforge.net Subject: Re: [Wicket-user] License for CMS (components) I'm very biased against LGPL. The letter of the license is not applicable for Java use, and LGPL is strongly at odds with Apache license. If at some time we would like to adopt such components when we arrive at Apache, then this will prohibit reusing any code from this project. I'm in favor of Apache 2, since that is what most Wicket projects are based on. I would use a license that is at least compatible with Apache. Martijn On 9/26/06, Che Schneider [EMAIL PROTECTED] wrote: Hi, My vote goes to LGPL: not as restrictive as GPL but preserves the gist of it. :) // Che -Original Message-From: [EMAIL PROTECTED][mailto:[EMAIL PROTECTED] ] On BehalfOf Ted Roeloffzen Sent: Tuesday, September 26, 2006 2:13 PMTo: wicket-userSubject: [Wicket-user] License for CMS (components) Hello all, We are going to create a Wicket CMS and/or CMS Components,but we are not sure under which license to do this. Whichlicense would you prefer? BSD, Apache, (L)GPL or another one? greets, Ted__DISCLAIMER: This e-mail message is intended for the addressee(s) or authorized recipient only. If you are not theaddressee, or an authorized recipient, you are specificallyadvised that any use, distribution, publication, copying or repetition of this information is prohibited. If you havereceived this information in error, please notify usimmediately (+31 (0)20 50 25 800) and destroy this message.__DISCLAIMER: This e-mail message is intended for theaddressee(s) or authorized recipient only. If you are not the addressee, or an authorized recipient, you are specificallyadvised that any use, distribution, publication, copying orrepetition of this information is prohibited. If you have received this information in error, please notify usimmediately (+31 (0)20 50 25 800) and destroy this message. __ DISCLAIMER: This e-mail message is intended for the addressee(s) or authorized recipient only. If you are not the addressee, or an authorized recipient, you are specifically advised that any use, distribution, publication, copying or repetition of this information is prohibited. If you have received this information in error, please notify us immediately (+31 (0)20 50 25 800) and destroy this message. -- --- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforge CID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- a href="" href="http://www.thebeststuffintheworld.com/vote_for/wicket" target="_blank" > http://www.thebeststuffintheworld.com/vote_for/wicketVote/a for a href="" href="http://www.thebeststuffintheworld.com/stuff/wicket" target="_blank" > http://www.thebeststuf
Re: [Wicket-user] License for CMS (components)
Hi Martijn, Well said - I did not think about that. And agreed, you might very well run into that problem. I admit that I have not had a thorough look at the Apache license but only 'read over it' and found it to be too 'open' for my liking: if you use an Apache-d software, you can keep the whole source secret, you can have it all open source, whatever. :) On the other hand, is it not true that Apache 2 is compatible with GPL? *mental note: read Apache and Apache 2 again* // Che -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martijn Dashorst Sent: Tuesday, September 26, 2006 2:32 PM To: wicket-user@lists.sourceforge.net Subject: Re: [Wicket-user] License for CMS (components) I'm very biased against LGPL. The letter of the license is not applicable for Java use, and LGPL is strongly at odds with Apache license. If at some time we would like to adopt such components when we arrive at Apache, then this will prohibit reusing any code from this project. I'm in favor of Apache 2, since that is what most Wicket projects are based on. I would use a license that is at least compatible with Apache. Martijn On 9/26/06, Che Schneider [EMAIL PROTECTED] wrote: Hi, My vote goes to LGPL: not as restrictive as GPL but preserves the gist of it. :) // Che -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ted Roeloffzen Sent: Tuesday, September 26, 2006 2:13 PM To: wicket-user Subject: [Wicket-user] License for CMS (components) Hello all, We are going to create a Wicket CMS and/or CMS Components, but we are not sure under which license to do this. Which license would you prefer? BSD, Apache, (L)GPL or another one? greets, Ted __ DISCLAIMER: This e-mail message is intended for the addressee(s) or authorized recipient only. If you are not the addressee, or an authorized recipient, you are specifically advised that any use, distribution, publication, copying or repetition of this information is prohibited. If you have received this information in error, please notify us immediately (+31 (0)20 50 25 800) and destroy this message.__ DISCLAIMER: This e-mail message is intended for the addressee(s) or authorized recipient only. If you are not the addressee, or an authorized recipient, you are specifically advised that any use, distribution, publication, copying or repetition of this information is prohibited. If you have received this information in error, please notify us immediately (+31 (0)20 50 25 800) and destroy this message. __ DISCLAIMER: This e-mail message is intended for the addressee(s) or authorized recipient only. If you are not the addressee, or an authorized recipient, you are specifically advised that any use, distribution, publication, copying or repetition of this information is prohibited. If you have received this information in error, please notify us immediately (+31 (0)20 50 25 800) and destroy this message. -- --- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforge CID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- a href=http://www.thebeststuffintheworld.com/vote_for/wicket;Vote/a for a href=http://www.thebeststuffintheworld.com/stuff/wicket;Wicket/a at the a href=http://www.thebeststuffintheworld.com/;Best Stuff in the World!/a -- --- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforge CID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user __ DISCLAIMER: This e-mail message is intended for the addressee(s) or authorized recipient only. If you are not the addressee, or an authorized recipient, you are specifically advised that any use, distribution, publication, copying or repetition of this information is prohibited. If you have received this information in error, please notify us immediately (+31 (0)20 50 25 800) and destroy this message
[Wicket-user] License for CMS (components)
Hello all,We are going to create a Wicket CMS and/or CMS Components, but we are not sure under which license to do this. Which license would you prefer? BSD, Apache, (L)GPL or another one?greets,Ted - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] License for CMS (components)
HOWTO: Pick an open source license http://www.theserverside.com/news/thread.tss?thread_id=40946 Regards, Erik. Ted Roeloffzen schreef: Hello all, We are going to create a Wicket CMS and/or CMS Components, but we are not sure under which license to do this. Which license would you prefer? BSD, Apache, (L)GPL or another one? greets, Ted -- Erik van Oosten http://www.day-to-day-stuff.blogspot.com/ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] License for CMS (components)
Hi, My vote goes to LGPL: not as restrictive as GPL but preserves the gist of it. :) // Che -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ted Roeloffzen Sent: Tuesday, September 26, 2006 2:13 PM To: wicket-user Subject: [Wicket-user] License for CMS (components) Hello all, We are going to create a Wicket CMS and/or CMS Components, but we are not sure under which license to do this. Which license would you prefer? BSD, Apache, (L)GPL or another one? greets, Ted __ DISCLAIMER: This e-mail message is intended for the addressee(s) or authorized recipient only. If you are not the addressee, or an authorized recipient, you are specifically advised that any use, distribution, publication, copying or repetition of this information is prohibited. If you have received this information in error, please notify us immediately (+31 (0)20 50 25 800) and destroy this message.__ DISCLAIMER: This e-mail message is intended for the addressee(s) or authorized recipient only. If you are not the addressee, or an authorized recipient, you are specifically advised that any use, distribution, publication, copying or repetition of this information is prohibited. If you have received this information in error, please notify us immediately (+31 (0)20 50 25 800) and destroy this message. __ DISCLAIMER: This e-mail message is intended for the addressee(s) or authorized recipient only. If you are not the addressee, or an authorized recipient, you are specifically advised that any use, distribution, publication, copying or repetition of this information is prohibited. If you have received this information in error, please notify us immediately (+31 (0)20 50 25 800) and destroy this message. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] License for CMS (components)
It is true that a company can take the source code and make it closed and sell it with a new label when using Apache license. Personally I don't mind and there are a lot of people that don't mind either. The problem with taking the ASL product, rebrand it and market it is that the product will always be behind what the free version provides, as long as the community is active and participating. I don't consider GPL or LGPL to be evil, they are just not my cup of tea. Martijn On 9/26/06, Che Schneider [EMAIL PROTECTED] wrote: Hi Martijn, Well said - I did not think about that. And agreed, you might very well run into that problem. I admit that I have not had a thorough look at the Apache license but only 'read over it' and found it to be too 'open' for my liking: if you use an Apache-d software, you can keep the whole source secret, you can have it all open source, whatever. :) On the other hand, is it not true that Apache 2 is compatible with GPL? *mental note: read Apache and Apache 2 again* // Che -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martijn Dashorst Sent: Tuesday, September 26, 2006 2:32 PM To: wicket-user@lists.sourceforge.net Subject: Re: [Wicket-user] License for CMS (components) I'm very biased against LGPL. The letter of the license is not applicable for Java use, and LGPL is strongly at odds with Apache license. If at some time we would like to adopt such components when we arrive at Apache, then this will prohibit reusing any code from this project. I'm in favor of Apache 2, since that is what most Wicket projects are based on. I would use a license that is at least compatible with Apache. Martijn On 9/26/06, Che Schneider [EMAIL PROTECTED] wrote: Hi, My vote goes to LGPL: not as restrictive as GPL but preserves the gist of it. :) // Che -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ted Roeloffzen Sent: Tuesday, September 26, 2006 2:13 PM To: wicket-user Subject: [Wicket-user] License for CMS (components) Hello all, We are going to create a Wicket CMS and/or CMS Components, but we are not sure under which license to do this. Which license would you prefer? BSD, Apache, (L)GPL or another one? greets, Ted __ DISCLAIMER: This e-mail message is intended for the addressee(s) or authorized recipient only. If you are not the addressee, or an authorized recipient, you are specifically advised that any use, distribution, publication, copying or repetition of this information is prohibited. If you have received this information in error, please notify us immediately (+31 (0)20 50 25 800) and destroy this message.__ DISCLAIMER: This e-mail message is intended for the addressee(s) or authorized recipient only. If you are not the addressee, or an authorized recipient, you are specifically advised that any use, distribution, publication, copying or repetition of this information is prohibited. If you have received this information in error, please notify us immediately (+31 (0)20 50 25 800) and destroy this message. __ DISCLAIMER: This e-mail message is intended for the addressee(s) or authorized recipient only. If you are not the addressee, or an authorized recipient, you are specifically advised that any use, distribution, publication, copying or repetition of this information is prohibited. If you have received this information in error, please notify us immediately (+31 (0)20 50 25 800) and destroy this message. -- --- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforge CID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- a href=http://www.thebeststuffintheworld.com/vote_for/wicket;Vote/a for a href=http://www.thebeststuffintheworld.com/stuff/wicket;Wicket/a at the a href=http://www.thebeststuffintheworld.com/;Best Stuff in the World!/a -- --- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforge CID=DEVDEV
Re: [Wicket-user] License for CMS (components)
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Agreed. Apache or BSD is my vote. I'm much less likely to use anything under the (L)GPL license. IMNSHO, that the LGPL preserves the gist of the GPL isn't a good a thing. ;) Martijn Dashorst wrote: I'm very biased against LGPL. The letter of the license is not applicable for Java use, and LGPL is strongly at odds with Apache license. If at some time we would like to adopt such components when we arrive at Apache, then this will prohibit reusing any code from this project. I'm in favor of Apache 2, since that is what most Wicket projects are based on. I would use a license that is at least compatible with Apache. Martijn On 9/26/06, Che Schneider [EMAIL PROTECTED] wrote: Hi, My vote goes to LGPL: not as restrictive as GPL but preserves the gist of it. :) // Che -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ted Roeloffzen Sent: Tuesday, September 26, 2006 2:13 PM To: wicket-user Subject: [Wicket-user] License for CMS (components) Hello all, We are going to create a Wicket CMS and/or CMS Components, but we are not sure under which license to do this. Which license would you prefer? BSD, Apache, (L)GPL or another one? greets, Ted __ DISCLAIMER: This e-mail message is intended for the addressee(s) or authorized recipient only. If you are not the addressee, or an authorized recipient, you are specifically advised that any use, distribution, publication, copying or repetition of this information is prohibited. If you have received this information in error, please notify us immediately (+31 (0)20 50 25 800) and destroy this message.__ DISCLAIMER: This e-mail message is intended for the addressee(s) or authorized recipient only. If you are not the addressee, or an authorized recipient, you are specifically advised that any use, distribution, publication, copying or repetition of this information is prohibited. If you have received this information in error, please notify us immediately (+31 (0)20 50 25 800) and destroy this message. __ DISCLAIMER: This e-mail message is intended for the addressee(s) or authorized recipient only. If you are not the addressee, or an authorized recipient, you are specifically advised that any use, distribution, publication, copying or repetition of this information is prohibited. If you have received this information in error, please notify us immediately (+31 (0)20 50 25 800) and destroy this message. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - -- Justin Lee http://www.antwerkz.com AIM : evan chooly Skype : evanchooly -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (Cygwin) iD8DBQFFGR+IJnQfEGuJ90MRA4LVAKDpea3D/D8fQ2suEySNb7TiQvn2QQCfS4tG LijHNIDUVKmJ1q2EWAqi9Qk= =neXT -END PGP SIGNATURE- - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] License for CMS (components)
I'm very biased against LGPL. The letter of the license is not applicable for Java use, and LGPL is strongly at odds with Apache license. If at some time we would like to adopt such components when we arrive at Apache, then this will prohibit reusing any code from this project. I'm in favor of Apache 2, since that is what most Wicket projects are based on. I would use a license that is at least compatible with Apache. Martijn On 9/26/06, Che Schneider [EMAIL PROTECTED] wrote: Hi, My vote goes to LGPL: not as restrictive as GPL but preserves the gist of it. :) // Che -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ted Roeloffzen Sent: Tuesday, September 26, 2006 2:13 PM To: wicket-user Subject: [Wicket-user] License for CMS (components) Hello all, We are going to create a Wicket CMS and/or CMS Components, but we are not sure under which license to do this. Which license would you prefer? BSD, Apache, (L)GPL or another one? greets, Ted __ DISCLAIMER: This e-mail message is intended for the addressee(s) or authorized recipient only. If you are not the addressee, or an authorized recipient, you are specifically advised that any use, distribution, publication, copying or repetition of this information is prohibited. If you have received this information in error, please notify us immediately (+31 (0)20 50 25 800) and destroy this message.__ DISCLAIMER: This e-mail message is intended for the addressee(s) or authorized recipient only. If you are not the addressee, or an authorized recipient, you are specifically advised that any use, distribution, publication, copying or repetition of this information is prohibited. If you have received this information in error, please notify us immediately (+31 (0)20 50 25 800) and destroy this message. __ DISCLAIMER: This e-mail message is intended for the addressee(s) or authorized recipient only. If you are not the addressee, or an authorized recipient, you are specifically advised that any use, distribution, publication, copying or repetition of this information is prohibited. If you have received this information in error, please notify us immediately (+31 (0)20 50 25 800) and destroy this message. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- a href=http://www.thebeststuffintheworld.com/vote_for/wicket;Vote/a for a href=http://www.thebeststuffintheworld.com/stuff/wicket;Wicket/a at the a href=http://www.thebeststuffintheworld.com/;Best Stuff in the World!/a - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
