-
Google Web Toolkit Goes Fully Open Source (4 messages)
- Posted by: Bruce Johnson
- Posted on: December 12 2006 13:44 EST
The Google Web Toolkit team announced today that the project is now fully open source under an Apache 2.0 license. I wasn't kidding when I said that we would periodically revisit the question of open-sourcing Google Web Toolkit. The team has announced today that the project is now fully open source under an Apache 2.0 license. The new 1.3 RC has no new features since 1.2, but the team is taking this open source thing seriously by vowing to discuss and develop in full public view. In addition to simple directions for compiling the source yourself, the updated site includes the often-requested development roadmap as well. How does Google Web Toolkit being open source affect you? Did you care either way? And do you think you will participate on the contributors forum?Threaded Messages (4)
- Re: Google Web Toolkit Goes Fully Open Source by Stephane TRAUMAT on December 12 2006 17:28 EST
- Re: Google Web Toolkit Goes Fully Open Source by Berry Crawford on December 12 2006 18:10 EST
- Why Apache License? Why not GPL or LGPL? by Samia Fn on December 13 2006 00:59 EST
- Re: Why Apache License? Why not GPL or LGPL? by Casual Visitor on December 13 2006 09:17 EST
-
Re: Google Web Toolkit Goes Fully Open Source[ Go to top ]
- Posted by: Stephane TRAUMAT
- Posted on: December 12 2006 17:28 EST
- in response to Bruce Johnson
For me, it's a great news ! I love GWT and we are using for our clients projects... I was still a bit scared about the licence... With a closed source software, I can secure my client because, what would happend if google stopped the project ? With open source, I can guarantee the investissment is safe for years and we could maintain it no matter what happend. -
Re: Google Web Toolkit Goes Fully Open Source[ Go to top ]
- Posted by: Berry Crawford
- Posted on: December 12 2006 18:10 EST
- in response to Bruce Johnson
Good for them! Well done. -
Why Apache License? Why not GPL or LGPL?[ Go to top ]
- Posted by: Samia Fn
- Posted on: December 13 2006 00:59 EST
- in response to Bruce Johnson
Isn't it easier to have incompatible derived works? Is everyone, including Google, allowed to create a derived but closed-source work, if I contributed something to it? -
Re: Why Apache License? Why not GPL or LGPL?[ Go to top ]
- Posted by: Casual Visitor
- Posted on: December 13 2006 09:17 EST
- in response to Samia Fn
Isn't it easier to have incompatible derived works?
Different Open Source 'philosophies' exist. Obviously both, (L)GPL and Apache work but for different user groups.
Is everyone, including Google, allowed to create a derived but closed-source work, if I contributed something to it?