"Manfred Usselmann" <[EMAIL PROTECTED]> schrieb: > You mentioned that you need to postpone this presentation. > Maybe you can give us some more details and explain the situation a > little bit? Have you come across any unforeseen technical issues? Not yet. So far everything looks promising. We even have the first customer who is working on a Tine 2.0 based installation.
> Or is > it just a minor delay as a result of the usual time restraints we all > suffer from from time to time? Yes. > When do you expect it to become ready according to your current planning? I'm not sure. At least not this month. > I myself would also be interested to know what exactly to expect from > your prototype. What are your criteria which define the readiness for > the discussion and voting? What do you want to achieve until then? The longer I have been thinking about this topic, the less sure I'm about what we should vote. Should we vote about which code line to use? That makes not much sense to me. Have a look at the pERP and BlueERP developers. They have bet their whole application on eTemplate. As long Ralf will not migrate eTemplate, these developers can only vote against our complete proposal, as they need to protect their investment too. Maybe we can vote if Tine 2.0 will be the technical base for eGroupWare 2.0. That would make sense maybe. As it would allow us to continue to improve Tine 2.0 and share as much as possible code in the distant future with the eGroupWare codeline. Do we need to vote at all about the old codebase against Tine 2.0? We need to find a way how we can work together. Not to vate against each other. We need to find common technical goals and solutions. And that's something Tine 2.0 is very good for. It's working code. You can have a look at and learn how we can improve the old eGroupWare 1.x codebase. The current codebase of eGroupWare 1.x is broken by design, if you apply the standards from today. It was good for PHP3 and PHP4, but compared with the possibilities PHP5 (and PHP6 in the future) can provide us, it is just broken. Any developer can have a look at our codebase, to learn how we can make it better. These ideas don't mean that we fear the vote. If the developers decide against our codebase, we have no problem with that decision. What do we like to achieve? - future-proof codebase - codebase which uses standard PHP designpatterns - PHP5 codebase - unit tests are very important for us - common rules how to write/format the code - get the javascript gui done - database setup - maybe something more -- 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 ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ eGroupWare-core mailing list eGroupWare-core@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/egroupware-core
