Hi Manfred,
I already wrote this post this morning, I resended it 3 times, nabble is telling me it’s not accepted, so I’ll give it onw last try making a new answer (hope that it was a technical problem and not some way to make me shut up)
ManfredU wrote:
"> technical experienced users (not to use the word Geeks) use egw. If
> egw should be used by "normal" users, too, the projects fail most of
> the time, because people just will not use the software.
Improving usability is a good thing, don't you think so? And allways a
topic especially for web application and does not only apply to eGW.
Look at all the discussions about web mail clients..."
that’s a very general statement, I cannot object, but this was not a topic I discussed.
you cited:
"
I think the question to be discussed here is not, if some of the
problems with egw Lars and Conny mentioned are true or not,
To me it makes a big difference. If they are true it should be possible
to talk about them in an open source project. Isn’t that the meaning of
’open’? Do you think that public technical discussions should be
forbidden?
"
you missed
"
but if
project members should be aloud to give semi-official interview
stressing the disadvantages of egw this much."
So of course, I think a technical discussion should not be forbidden (this is exactly what I tried to say). But the developers list is the place for technical discussions, which already was made clear least but not last by the admin statement.
But press-releases and interviews focussing on the problems on egw and giving a very irritating picture of egw to the public (tine is just a place were to check out new technologies at the moment).
This interview would be quite nice for an election campaign, why tine should be egroupware2.0 but an interview is not the place for an election campaign.
ManfredU wrote:
And the way concurrent updates are handled is an important aspect
of multi user applications. Well, you may not find such kind of
information in the selling brochure but you should expect it to be part
of the training material even for commercial products.
As I already stated, I don’t want to discuss the technical points here. In fact I agree with some of them. But that’s not the point. The point it, that the Metaways people, already stirred up the user-list and the News etc. advertising for tine and not stopping pointing out the problems with egw all over again (without being able to present a sufficient alternative, perhaps they will be able to in a couple of month) But the general problem, that they choose to drop even database structure will make all migrations very, very difficult. So every body agrees on some points they mentioned, it’s not the question if there should be innovation- as they are trying to tell all old-egw is thinking- but whether the way they chose is they best way for the project.
They were forbidden to do this (admin statement) and told to keep this technical discussion on the dev-list.
Now, they are not mailing to the userlist anymore, no they are giving public interviews!
I really think it’s time to defend the rules this project is based on.
best regards Frank
