"Oscar Manuel Gómez Senovilla" <[EMAIL PROTECTED]> schrieb: > Why not allow the Metaways developers keep *investigating* in extjs (or > whatever) as long as they change the domain (which they already did) but > don't bind it in any way to egw? What will happen only time within some > months will decide, but trying to exclude it *right now* I think it's an > error. I also think it's a mistake trying to decide *right now* that > "tine" is *the only* way for future egw, apart from not allowing any > kind of compliance with current egw api. Maybe in, let's say, one year, > current egw api uses some new api/framework/whatever that makes possible > to reach a common intermediate point that, if the tine team still keeps > developing and on their belief for unique possible way, at least there's > a way to reach integration. And if not in one year, in two years, then > three, etc. And maybe the current egw framework has found another way > that's even more powerful than others. The summary is that everything > can happen in the future in any of both sides.
Hello Oscar! Just to state it again, as many developers still did not understand what we are doing. In the summer we sat together with Ralf, try to talk with him about our ideas, how Cornelius and I like to improve the CURRENT codebase of eGroupWare. At this time Cornelius was not a Metaways employee and it was also never planed that he will become one. At this meeting Ralf and Nigel Vickers from Stylite denied any of our requests how to we liked to improve the CURRENT codebase of eGroupWare. Because Ralf and Nigel denied any of our ideas, we have started our own codebase on our own servers. Now we are working on a proof of concept, how we think eGroupWare can work and look like in the future. This will allow the other developers in the project to decide themself, if our ideas are good or not. This proof of concept is limited to 4 applications and will have no backward compatibility. It's a proof of concept. When we have finished the proof of concept(scheduled for the first quarter 2008) and we like to have a vote, if the other developers like our codebase or not. If the other developers like our codebase, we can start thinking about how we can add backwardcompatibility and we can start talking about a longterm migration path. We are working for eGroupWare not against. Currently we need to learn about ExtJS, JavaScript and JSON. It simply makes no sense in the current state to talk about backwardcompatibility. We can do only one step after the other. It makes no sense to repeat the same errors, I did already with FeLaMiMail. -- Lars Kneschke CTO OfficeSpot.Net Metaways Infosystems GmbH Pickhuben 2-4, D-20457 Hamburg eGroupWare Support: http://www.egroupware-support.net OfficeSpot.Net Collaboration Server: http://cs.officespot.net our proposal for the next major eGroupWare release: http://www.tine20.org E-Mail: mailto:[EMAIL PROTECTED] Web: http://www.metaways.de Tel: +49 (0)40 317031-21 Fax: +49 (0)40 317031-921 Mobile: +49 (0)175 9304324 Metaways Infosystems GmbH - Sitz: D-22967 Tremsbüttel Handelsregister: Amtsgericht Ahrensburg HRB 4508 Geschäftsführung: Hermann Thaele, Lüder-H.Thaele ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ eGroupWare-core mailing list eGroupWare-core@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/egroupware-core
