107
I think, you can already learn:
Current project management and communication policy is something like:
"All we do is Big Secret, which we do as we think is better... don't worry, we know it better than you... which will be opened when somebody decided 'it's good time for'"
Developers don't think about permanent and transparent communications as "must have" for project's vitality and seems even don't know, that is responsibility in big project.
Responsibility is not only write good code, but also respect users and support user's choice by
- having
- publishing
strategic and tactic plans, informaton about project life and changes, which can affect users("Where is Scalpa?", "Why Mith silently disappeared?", "What you (Team) will do this month|this quarter?" etc.. etc...)
Now XOOPS devs position itself by the infallible gods, who prophesy to the flock from the unattainable heights, when it implores the miracle.
This "unique" policy generate most of problems and questions... XOOPS Development team not open for communication with users, they forgot simplr thing - they are (and XOOPS) are nothing, zero, without users, which used-use (?)-will use (?!?!) product...
Weak management, poor organisation, the unwillingness to think to the step forward, the unwillingness to learn on the examples of the more transparent and more organized projects. The exaggerated pride and the overstated self-appraisal is the lightest diagnosis, which I can write down into the therapeutic map
