DaveL's Proposal

The article The XOOPS Foundation Manifesto coincides with my viewpoint on this subject.

[edit]

Flowchart

http://www.moorey.net/images/organisational_charts/H.jpg

[edit]

The Project

1. The Project (core development team) handles core development.

[edit]

The Community

2. The Community handles everything else, including addons (modules and themes) and user documentation and support.

[edit]

The Foundation

3. The Foundation supports the Project and the Community by providing resources.

[edit]

Overall management

There should be no overall management. The three components of the "trinity" work independently and cooperatively.

[edit]

responsibilities

There are some joint responsibilities. Examples:

[edit]

Documentation

a. Documentation on the XOOPS core would probably be a collaborative effort of the Project and the Community.

[edit]

Managed by the Community

b. Most areas on *.xoops.org would be managed by the Community. But the Project might manage an area for posting news about new core releases and discussing core development. In either case, the Foundation, which pays for the server, controls server access, and is the authority that decides when to delegate that access to someone else.

BACK to Proposal

Retrieved from "http://www.xoops.org/modules/mediawiki/index.php/Proposals-DaveL"

This page has been accessed 590 times. This page was last modified 23:43, 25 December 2007. Content is available under XOOPS Project.