Hi devs,After a hard period (again) of flameing and fighting, we want to make a proposal to solve the situation(s).
In our view the current state is the following:- The majority of egw devs and users don't want to continue this ugly flame war.
- On the other hand, also nobody wants to have the votes conny proposed. - No one wants to drop (not even lars or conny) egw 1.x- Also a big majority don't want to drop Tine 2.0 out of the egroupware.org project.
So here is, what we propose:- Lets have two emancipated codelines within the framework of the egroupware.org project. - Both activities share the same goal, to provide great collaboration software based on free and open sources. - If possible, both activities agree on common technical standards and implement them in a compatible way
- Tine cares for smooth migration paths from egw to tine- eGW 1.x (may) ports back new technologies from tine when they where proven successfully there. - Both activities decide on their own about new members, coding- standards, and quality agreements. - On both web-sites, we'll link each other in a friendly way, e.g. by aggregating the news feed of the other page.
We propose to freeze this state for about half a year, before we continue to discuss about project politics. Hopefully then in a kind and friendly manner.
We feel, that continuing the discussions don't lead to any valuable result. So this is our last attempt. If it fails we will take the Tine effort out of the egroupware.org project.
cu Lars, Thomas, Matthias and Conny
tine_egw_relation
Description: Binary data
------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/egroupware-core
