XOOPS Cube Development Roadmap

The “XOOPS Cube” is a fork version of the XOOPS. This document briefly describes where the XOOPS Cube project has been, and then details where it is going. This roadmap direct where the project is going, however, this document may be amended upon needs of users and developers.

Background:
The XOOPS has been developed from the beginning of 2002, forked from php-nuke. The XOOPS 2.0.x development team, lead by Onokazu, set a high standard that is flexible and adaptable to a wide range of uses. Thus, 3rd party developers and designers can work on extensions and implementations, while the development team works on core development. The XOOPS get very popular nowadays. Many users from individuals to large organization, including government authorities and enterprises, use the XOOPS to fit their needs.
In the September 2003, a half-year after the XOOPS 2.0 had been shipped, new XOOPS development team has been discussed. It has ‘Core development team’, ‘theme design team’, ‘quality control team’, ‘document team’ and so on, aiming to get more impetus by role sharing. It resulted in confusion and delay of decision making to fix security bugs. In addition to that, it was a critical problem to Japanese and some others that there was some updates including disregards for use of multi-byte characters.
XOOPS JP team had proposed to take major part in XOOPS development. However, it was refused by the XOOPS team at www.xoops.org. The XOOPS JP team struggled in dysfunction for providing XOOPS which fit people’s needs in Japan.
Thus, XOOPS JP team had decided to provide a new version of the XOOPS (= XOOPS Cube) for the people who needs prompt security fix and true multi-byte support.

Direction:
We put first priority on multi-byte compatibility of the XOOPS Cube. Users who use single-byte characters are also welcome. We provide English and Japanese version of the XOOPS Cube. We also welcome developer, translator and community organizer from all the world. We keep basic principals such as user friendly interface and having fun experience for user and developers heretofore in the XOOPS Cube.
We try to develop keeping versatility of the new XOOPS fork, as it is used at various type of website from individual to enterprises.

In the relation to XOOPS offered from xoops.org, interchangeability at the module level with XOOPS 2.0.10 is secured. We will make effort to keep interchangeability with the XOOPS offered from xoops.org (version 2.0.10 and below), however, it is no guarantee to keep the interchangeability in future releases.

Xoops Cube ºËÐÄ¿ª·¢Ô±Ö®Ò» minahito µÄ blog

XOOPS Cube, XOOPS

¸ÃÎÄÕÂÆÀÂÛµÄRSS¡£
TrackBack URI