“randy” randy@roadwarriors.ca schrieb:
I think the power of egroupware has been in the past the unity of the
devs.
Machines will get faster and faster. It will lickly take years for egw2.0
to be fully utilized to the extent of egw and you have a split between
loyalties.
Is there not a middle ground? A slow rewrite of the egw api using zend?
Rewite of etemplate using json/extjs?
It is easier to start from scratch but the community you have built over
the
last couple of years is really amazing. I think maintaining that unity is
worth any compromise and that building a community like you devs have over
the years is harder then any coding challenge you might face trying to
compromise.
Hello randy!
We are 3 developers here at Metaways working full-time on eGroupWare 2.0.
These 3 developers earn no money for the company currently. As we need to
stop this very soon, we have don’t have the time to do a slow rewrite. If
you choose the slow incremental way or the fast direct way, the final goal
is always the same. Replacing the eGW api by the Zend Framework. Replacing
eTemplate by ExtJS.
Alone from the economical point of view, it is not possible for us to choose
the incremental way. It would take to much time and also cost to much money.
Let’s have a look from another point of view. I don’t need to rewrite the
code for eGroupWare during my workingtime. I can do it also in my spare
time. But my spare time is limited. Also from that point of view the slow
rewrite is not really a option for me.
We are pretty sure, that we can create a better product in a shorter time,
when we are starting the rewrite now, than doing the slow rewrite. It’s
simply more efficient for us.
If you search through the mailinglist archives you will (hopefully! :-))
find some emails from me from about 2 years ago, where I tried to start a
discussion about the future of eGroupWare. I don’t like to wait any longer.
Either I leave eGroupWare or I start to do something useful again. I choosed
the later option. I really tried to find a working compromise, but it was
not possible. Sorry, but I tried it really hard.
And I also don’t think that we will split the community. Sometimes you need
to make a break and need to look back, to find out what was good and what
was not good. And sometime you need to do something new. Need to learn about
new technologies. The web technologies we used 3 years ago are totally
different compared to the technologies we are using today. 3 years ago
website like youtube or google maps would not be possible. And that’s what
we are doing now. We try to solve the problems which keep eGroupWare from
evolving forward.
We are making a proposal and let the community decide, if they like it. The
old codebase is still there and Ralf is still maintaining it. From the users
point of view, there is no problem. If we(eGroupWare 2.0) have reached a
certain level, the user can decide if they want to migrate to the new
version or if the like to stay at old code base.
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
E-Mail: mailto:l.kneschke@metaways.de
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: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers
