42
Quote:
Mamba wrote:
Look, we had Skalpa and Herko in separate positions, and we know the result of it. It didn't work.
Let's not try to make it in stone one way or the other. There are success stories on both sides of the spectrum, as well as failures. In the end, it all comes to the person, and the people who support him. If he gets a good Council doing what they supposed to do, then he'll have less project management work.
Sorry Mamba, but with all due respect just because two people fail in many respects does not mean the next two people will do the same. The problem is that people here are unwilling to take any chances on the fact that we have had failures before. Well we might as well packup and all go home and not even bother.
The fact is there have been more council member elected and left than I care to count or remember, if that doesn't tell you something then nothing will. The problem is that the current mandate and policy is so far not bringing this community together but splitting it futher apart. We have a council in direct opposition from a self elected body that will not co-operate with the so called elected bodie of Xoops, doesn't this also tell you something?
Now if the problems were only the day to day running of this project then I may have agreed with you, but the fact is this JOB right now is not a one man task. If DJ wishes to be project leader then I suggest he hires a new lead core developer and concentrate on the task of bringing this project together, code and community wise.
I believe people actually underestimate the severity of the full task here at XOOPS and you all think that by electing a council that all the problems here at XOOPS will just fade away. The problem with XOOPS is that it has always had a weak leadership (Ono not included in this), with no real vision or leadership skills and that is why this project is in a mess.
I have seen many project handled by a project leaders who delegate tasks and is willing to work for the project rather than themselves.
ATB
Catz