25
Quote:
Mithrandir wrote:
Ok, this is getting a bit one-sided. GIJOE is not very visible here, but I am sure he does a tremendous job in the Asian community sites, so it is not the case of a guy just coding, coding and coding and not doing any support work.
GIJOE is the most active supporter in Japan. Moreover, he couldn't be more active in his personal support site as you can see.
Quote:
carnuke wrote:
As this new year starts, let's invite some positive constructive response to this discussion in a way that all parties feel they are heard, appreciated and respected.
I quite agree with you. As Mithrandir stated on the news, XOOPS seems to be looking for the developers for the current version. At the same time, Japanese developers seem to be serious about leaving XOOPS and making their own one.
So why don't you make the best of Japanese developers' enthusiasm? For instance, you can let the Japanese team alter the current 2.0.x series. And the others focus on the 2.1 series.
Of course, there should be a consensus for the development so as not to make a difference between the current and the future one in their features.
This may delay the release of 2.1, eventually. But even Onokazu thinks there should be another release with a few, but not too radical, changes in the feature before 2.1 arrives.
In the end, all the Xoopsers can have more secure Xoops, Japanese team doesn't need to worry about the language, and English team can focus on the future version.
Surely, I'm not ignoring the other local communities. But Japanese developers are just HEATED in many ways.
This is "ORETEKI Xoops":
http://marijuana.ddo.jp/xoops/modules/mydownloads/http://marijuana.ddo.jp/xoops/modules/mydownloads/visit.php?cid=1&lid=20&type=0Some modules have already exceeded the standards of the core, I think. So it's high time we thought how to adopt these advanced features to the core, isn't it?