Hi!
> I'm a victim of Ext, LLC which bait and switched("Screwed") the ExtJS
> community several months ago. I've questions regarding Qooxdoo("Decent
> looking toolkit") for the good of a open source, free, community
> contributed, and free-to-use-for-non-open-source work.
>
>
> I'm a IT Specialist and Software Engineer, working on some applications
> right now while trying to make a choice. I've starting to work more on
> user interfaces and must make a choice which will affect much of my
> work. I want to be part of a project which I can use for free without
> fear of being victimized by a company and want the ability to contribute
> without signing my rights away.
Sorry to hear about your bad experience with ExtJS and their dramatic
shift in licensing terms. Anyway, welcome to qooxdoo, I'm sure you'll be
surprised what qooxdoo has to offer. ;-)
> My questions below are brought up after I was victimized by Ext LLC, ran
> by Jack Slocum("Scammer"), in to thinking ExtJS was an open source
> project with low risk.
A lot has already been written about those repeated license changes in
ExtJS, so I prefer not to add any judgement here. But it is clear that
one shouldn't mess with Open Source and its licensing. qooxdoo only uses
the unmodified OSI-approved licenses LGPL and EPL,
http://www.opensource.org/
> 1) Who owns qooxdoo?
qooxdoo was initiated as an Open Source project in 2005 and is actively
supported and maintained ever since by 1&1 Internet AG, the world's #1
web host. There is a team of full-time developers dedicated to qooxdoo
framework development. For more info, checkout
http://qooxdoo.org/about/developers
> 2) If I contributed a module and licensed the code under the qooxdoo
> license arrangement, do I still keep my rights?
Yes, if you are talking about "copyright", you would be the copyright
holder. You then choose the licensing for your contribution, which
should make clear how your code may be used. We suggest to use the same
licensing terms as qooxdoo's dual license LGPL/EPL, if your code allows
for that. If it only allows for either one, make that restriction clear.
Any other OSI-approved Open Source license that is compatible to this
dual license (e.g. liberal license like BSD or MIT) is fine as well.
Also see http://qooxdoo.org/license
> 3) In relation to question two, do I have to sign away my rights to the
> code to another company for a contribution?
No, qooxdoo is a true Open Source project, i.e. we like your code, not
your rights. ;-) Unlike many other JS frameworks we also have public SVN
repositories. So you can monitor the state of the project at any minute
without having to wait for the next "official" release.
Everybody is welcome to contribute. For instance, we set up and keep
improving an appropriate infrastructure called qooxdoo-contrib
http://contrib.qooxdoo.org that allows for an easy development of and
collaboration on contributions, including SVN support and own release
management for contrib maintainers.
> Those are my main concerns, other information which I've searched for
> already has been answered by documentation and the mailing list archives.
Fine. If there is any information missing or questions still unanswered,
please let me know,
Andreas
PS: I'm not a lawyer. Please make sure you read and understand the
licensing terms of qooxdoo!
--
Andreas Ecker
Project Lead
http://qooxdoo.org
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
