Quote:
to understand what is going on
Or get the wrong end of the stick by stiching things and fragments together from here and there.
OK, I had hoped it would fit in with a better time, better format and better message, but here it is:
As you can guess by reading about a possible XOOPS fork by a team of Japanese developers including Onokazu, you can also guess that he is no longer a XOOPS core developer.
This decision was made by a majority in the XOOPS Core Team after I asked them to decide on the issue.
My reasons for asking for a decision on such a critical question were that my ideas and way of coding is incompatible with Kazu's and have been for quite a while, culminating in Kazu's implementation of a security token system that was not as easy to implement in modules as it could be - and the subsequent discussion which got both too public and too much out of hand with one side being emotional and rude and the other side being deaf.
That is not a way to progress and after talking with Skalpa, I could conclude that 2 out of 3 members of the core development team could work together and not with the third.
So something had to be done and that was what we did. We want what is best for XOOPS and 2 people working in one direction and another working in another will only result in a higher degree of roll-backs, code re-writings and similar setbacks.
I had hoped that Kazu would instead focus his efforts on bringing the ideas from the Japanese community closer to the core development - without implementing them directly and personally - but apparently this is not the case. I still wish he will do that instead of forking XOOPS. As this thread has also highlighted, we are in dire need of a Japanese-English proficient person who can be the link between us and the Japanese community - and Kazu definitely have the proficiencies to do that.
In the meantime, I have focused on getting the development of XOOPS 2.1 on the road to show that XOOPS development does not stop with Kazu - on the contrary. It is also not a one-man show with the actor changing from Kazu to myself - the brotherpart of the implemented bugfixes, patches and features are based on ideas, code and reports from the community - and at this point, there are several developers not in the official core development team working on parts of the 2.1 core in order to tweak and polish the flow, so the inconveniences in the 2.0.x core will be a thing of the past.
We have a group of people working on proposals on how to improve communication between local support sites. We have people working on how to promote XOOPS in the outside world. XOOPS is finally becoming a team effort in all aspects and noone should doubt whether there is a future for XOOPS. The 30.000 registered users on xoops.org will make sure that there will be.
