Hej Stefan! On Tue, 2010-09-14 at 11:45 +0200, Stefan Andersson wrote: > Hej Andreas! > > >> We have developed about 1,200,000 lines of "qooxdoo" code and > >> converted a system which soon will "fly"... We are satisfied about > >> it. > > >Wow, this is really impressive! Are you sure you really talk about > >"1,200,000 lines of code"? Even if that includes comments, this would > >make it by far the largest qooxdoo application at least I know of. > > Including comments. It is a "simple" bread and butter application, converted > from Java GUI.
Wait, you say at your business 21 developers work 100% of their time on such a qooxdoo app, and you call it a "simple bread and butter application"? > >I guess everyone would really interested in getting to know more about > >this huge qooxdoo project of yours. You repeatedly talk on the mailing > >list about "openness", being more transparent and so on. Unfortunately > >nobody (at least not me) knows either about your company or your > >project. :-( Why wouldn't you want to share it with the qooxdoo > >community?? > > Certainly, but it is not an open source project. This passing of yours is > repelling and I would > appreciate more diplomacy. Don't panic! Nobody is talking about making your app code publicly available. In most open source environments nobody would expect that, so why would you do? I was talking about telling the community what large-scale qoxodoo app development you do. Seriously, you successfully create and maintain a 1,200,000 LOC qooxdoo app with a team of 21 full-time people and you don't even disclose the name of the company or a description and/or screenshot of the app in the real-life examples? Being silent doesn't help qooxdoo at all. Well, fair enough. That is how open source should also be able to work (and that's why we make exactly that possible by choosing 2 liberal, approved licenses (LGPL/EPL), and not GPL). You actually don't seem to care about supporting and promoting qooxdoo by telling the world about your success story? Instead you demand more "openness" of qooxdoo? To whom should this project (core team, 1&1, contributors, community) be more open? You don't give anyone a clue of who you are. > Our development is not a question for the community and will never be. We > have in qooxdoo found > an excellent base for the web gui and that's it. Perfect. If 1&1 would have that very mind set, qooxdoo as it is simply wouldn't exist. Instead, the company and the core team puts a lot of effort into providing an enterprise-level framework. Totally for free to anyone. To me that is open source spirit. > We have in qooxdoo found > an excellent base for the web gui and that's it. That's it? Ok, so you simply are a consumer of qooxdoo, right? > >> The support is fast and mostly accurate. The core team is mostly very > >> skilled in its answers. But we would never choose qooxdoo for such a > >> big project without knowing we have our own resources if qooxdoo dies > >> or if the qooxdoo team disappears in some or the other way. Too big > >> investment and too big risk, if we wouldn't have the resources by > >> ourselves. > > >Sounds like you got many development resources behind your qooxdoo > >project. That is great, and an excellent opportunity for you to > >contribute back to the project. Have you ever thought of adding regular > >contributions to qooxdoo-contrib? It's a pretty straightforward process, > >you certainly have seen the recent contributions, so it also shouldn't > >be hard for your team. If you need any help with qooxdoo-contrib, > >http://contrib.qooxdoo.org, please let me know. > > 21 people 100% of time. > > We have chosen to contribute by asking questions, correcting bugs, adding > ideas and getting things > cleared out by the core team. > > If we will get more involved future will tell. Not the future will tell, you would have to tell. > Yes, we have a few things we could share with the community as contributions, > but until it is clear > how the policies of openness is we will wait for the right moment. I'm sure also just "a few things" out of your codebase would be appreciated by the qooxdoo community. I don't see any uncertainty about the "policies of openness". There are new contributions made to qooxdoo every week. Why wouldn't you be able to contribute? I suggest you become a contributor: you sign the regular license agreements, we then set you up with full SVN commit rights to qooxdoo-contrib, and then you can start right away. It's all in the docs, maybe you may want to reread the following: http://qooxdoo.org/contrib http://qooxdoo.org/documentation/general/faq http://qooxdoo.org/documentation/general/committers_guide If there is anything unclear, please let me know. Looking forward in you becoming an active part of the qooxdoo ecosystem. Andreas -- Andreas Ecker Project Lead http://qooxdoo.org ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
