Hi Burak, lets figure out some of the next steps that are relevant for your contribution.
> > > i can say that this code doesn't derive from mateo casati's client > > > anymore, it's rewritten. there are code fragments here and there, but > > > the logic is completely different. > > > > Then why do you maintain the copyright notices in the code and readme?! > > because i'm not sure, i'm no lawyer. as i said there are still code > fragments lying around here and there, so i try to be as honest as i > can. We need to be absolutely sure about the legal situation. Fair enough that you're not a lawyer. Nobody is here either, so don't worry. But I'd suggest you carefully re-evaluate what original source code might be left in the current code base. There's also some confusion about the licensing terms. Is the 3rd party code under GPL or CC-SA-2.5? The current 0.4.1 release of your Soap contribution is even covered by a BSD-style license. Please try to figure it out, even if I understand it isn't something a developer really wants to do. It simply is a minimum requirement when developing open source software. If you've got any legal questions, please contact me off-list, so I might be able to assist. Once the license issues are resolved (hope we get that straightened out soon), it would be great to advance your contribution as expected to make it really useful for others as well. I think it's a great addition to have your contribution provide a SOAP communication layer for qooxdoo. It's also a perfect addition to qooxdoo-contrib. There's a misinterpretation once in a while about the qooxdoo framework (you called it "mainstream") vs. the contributions. Let me say that _both_ are essential parts for qooxdoo as a whole. It certainly is an advantage to have an ecosystem for qooxdoo, that features an infrastructure for distributed software. While qooxdoo-contrib provides some pre-defined infrastructure (like project structure, or tooling) and policies (documentation, release management, etc.), there's quite some freedom for all developers to collaborate, maintain and release their projects. So projects don't have to be stuffed into a monolithic framework on a code level and be governed by the same set of rules. But it has always been a top priority to allow to include any contribution easily into anyone's custom project. Sure there's much room for improvement (e.g. proper exposure of some of the contributions), but we're working on that and there have been some major steps forward recently. It's just that one cannot have it all at once, so simply needs some time and hatching. Anyway, lets work out the open issues specific to your Soap client so that it can really become a valuable addition to the qooxdoo ecosystem. If you've got any specific questions, feel free to contact me directly. Bye, Andreas -- Andreas Ecker Project Lead http://qooxdoo.org ------------------------------------------------------------------------------ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
