[Savannah-hackers] savannah.gnu.org: submission of Xoops

[w4z004]

A package was submitted to savannah.gnu.org.
This mail was sent to address@hidden, address@hidden


Sergio Kohl <address@hidden> described the package as follows:
License: gpl
Other License: 
Package: Xoops
System name: xoops
This package wants to apply for inclusion in the GNU project

About the XOOPS Content Management System 
Considerable time was spent researching other CMS’s to determine what the most 
popular features of these systems were and how to go about building them. The 
XOOPS team will be implementing these features and more through a modular OO 
based core. This philosophy will accomplish our goals of making the XOOPS 
system flexible for both users and developers. 
Many of the developers on the core XOOPS team have been involved in one-way or 
another with other Content Management Systems, namely MyPHPNuke (MPN). What the 
XOOPS team learned from their MPN experience is that users want an easy to 
install, easy to use, feature complete system from the beginning and a clear 
open communications channel. 
The PostNuke (PN) team has built a fabulously large community with great a 
support channel but the XOOPS team has a different view of what constitutes a 
\"core\" content management system. What we’re seeing is that users don’t want 
to spend a lot of time installing modules, which is the philosophy of the 
PostNuke CMS. While modular systems are nice, it’s even nicer to have tested, 
integrated and functional modules. 
 
The XOOPS team believes our approach is geared more towards the average user or 
developer than any of the other content management systems. For the XOOPS team, 
we feel it\'s important to include as many modules as we can with our core 
package, much like MyPHPNuke but with an OO core like that of PostNuke. 
We also feel it’s extremely and equally important to make it as easy as 
possible for module developers to contribute other modules to the system.  
The Past - The XOOPS system was conceptually based off PHPNuke 4.4.1 and 
MyPHPNuke 1.8.5. Both of these systems are widely adopted throughout the CMS 
and weblog community. 
Going forward - XOOPS aims are to be very modular in it’s core design. With 
modularity being a design goal, traditional monolithic development techniques 
will not be utilized in developing the XOOPS core system. About 70 - 80 percent 
of the original phpNuke/MyPHPNuke code has been totally rewritten from the 
ground up in order to support our OO model.  
Object-oriented PHP has been adopted throughout the entire core package, thus 
the name XOOPS.   

It already exists and you can see it at http://www.xoops.org