It is not my habit to quote an entire message but I must take exception on this one.
You want to clarify: You haven't. What you've actually said to distill the entire content of this message is that you've effectively taken over.
1/ Tom and JMorris are thanked for their contribution and dismissed
2/ Herko never was.
3/ The XOOPS Council never was (and still isn't.)
4/ Despite your protestation that you are seeking Open Management, we still don't have any.
If my own personal experience in the last few weeks is anything to go by, this project is doomed to failure simply because you have taken too much on and in the wrong way.
You have quoted XOOPS Council as being a bar to the Module Developers team not being able to set up camp in a private forum ( as a way of gathering thoughts as a team [I beleive the core dev team are using third party methods of doing the same thing], prior to public consultation,) yet you here announce that XOOPS Council doesn't exist.
5/ You want Open communication.
Bring it on.
6/ You want Open development.
Development is the only word that I actually believe is true. The closed down shop that you presided over in the last year was certainly not open.
So D.J., you want openness. You got it. If you want to be the XOOPS leader, then you have a great number of bridges to cross yet.
For the benefit of those just listening in, as of 3 weeks ago, I was just a moderator. As of 8 months or so ago I was just an end user, albeit active in module development. I naively volunteered to be the Mod Dev Team leader in response to D.J.'s call to action, and have had to seriously reconsider that in the last few days.
I can back up everything I have said here either from public record or from responses to PM's (unfortunately the XOOPS PM system doesn't allow outgoing message to be kept.)
I give you a challenge:
Establish a XOOPS Council in the next two weeks. Forget core development, you want to be the leader .. so lead. The developers (good men all) can do their job. You do your self appointed one. If you can't do that, then retire and leave it to those who can.
A
Quote:
phppp wrote:
Thank JMorris for the inputs.
I would clarify a little bit to make it clear.
Quote:
JMorris wrote:
Prior to Skalpa’s departure from XOOPS, there were 5 members of the Management structure of XOOPS.
Skalpa (Core Development/Project Management)
Rowd (Core Development/WWW site manager)
Ana (Addons/Demo site manager)
Herko (Foundation Chairman/XOOPS Project Treasurer)
JMorris (Community site manager/Server Administrator)
The above should be described as "some people who were supposed to be responsible for a certain of tasks".
The only "structured management unit" for XOOPS Project was a XOOPS Project Council established more than one year ago.
The Council members included skalpa, phppp, JMorris and two others. JMorris quit very early. The Council itself had never been active, nor officially announced.
Before skalpa's departure, skalpa and me were project administrators. When he left he added JMorris as an administrator but he did not explain JMorris' role when he talked with me on MSN on the day of his departure. Anyway JMorris and me have been working happily and efficiently in the past weeks, and in the future, I believe.
Quote:
the current management structure of XOOPS is as follows:
JMorris (Project Manager)
Phppp (Core Development)
Herko (Foundation Chairman)
Tom (Marketing and Communications)
Foundation, currently represented by Herko, is never intended to be part of XOOPS "management structure" according to the nature of XOOPS Foundation based on Herko's explanation to me.
Currently the "management structure" is not available yet.
However during the transient period, I has been taking the lead role for establishing XOOPS Project teams and invited JMorris and tom as temporary council members to assist in the procedure, never with task assignments and specified areas. The temporary status for the new Project Council is about to close and their efforts in the past weeks are much appreciated.
In the past XOOPS has been suffered too much from its lack of communication and non-transparent management, just like the unknown "management structure" mentioned above.
It's time for us to move forward and to build XOOPS an open-source project upon open communication, open management and open development.
