Proposals-SailJapan

From XOOPS Web Application System

link to original post

sailjapan's Proposal

COMMENTS: here and on sailjapan's discussion page.

Flowchart

SailJapan Organisational Chart
http://www.moorey.net/images/organisational_charts/C.jpg

Introduction

The following is a proposal for a new model of XOOPS governance. It has been drawn up by the community co-ordination team, drawing heavily on ideas proposed and debated by members of the XOOPS community in this forum.

If community members care to voice their support for it, this proposal will be submitted to the Foundation and Project Council as the will of the community. The ball will then be in their court.

If community members feel the need to add to or subtract from this proposal, this forum is the place to do so.

Part 1: The Proposal:

.1.1 We the undersigned

1.1 We the undersigned, dedicated contributors to and users of XOOPS, request and require that the XOOPS Foundation and the XOOPS Project Council submit to the will of their peers in the community.

.1.2 Significant numbers of the community

1.2 Significant numbers of the community (*see signatories) have debated and drafted the following document, and now offer this proposal to end, once and for all, the crippling infighting and resultant damage that has been the bane of XOOPS over the past several years.

.1.3 We believe in the ability to

1.3 We believe in the ability to, and rights of, all those involved with XOOPS, from end-users to core developers, to manage this project in a mature and mutually beneficial way, with the ultimate goal of creating a new spirit of co-operation through which XOOPS can be promoted back to it's rightful position as the leading CMS. With this belief in mind, we propose the following:

Part 2: Structure:

.2.1. Work-Groups:

2.1.0- Work-Groups: 2.1.1- Community proposed Work-Groups will form the basis of the project.
2.1.2- Work-Groups will exist to make a contribution to the XOOPS project.
2.1.3- Work-Groups will be made up of at least 3 like-minded volunteers.

.2.2. the Co-ordinating Council:

2.2.0- the Co-ordinating Council
2.2.1- the Co-ordinating Council will be comprised of Work-Group representatives and will have one Chairperson.
2.2.2- the Co-ordinating Council will exist to empower all Work-Groups to realise their contributions to the project.
2.2.3- the Co-ordinating Council will act as guide and arbitrator in times of dispute.

Part 3: Operation:

3.1.0- Work-Groups:
3.1.1- Work-Groups will be self governing. (*see appendix A)
3.1.2- Work-Groups will nominate one member to represent them on the Co-ordinating Council.
3.1.3- If a work-group forms but it's role is not initially seen as necessary, no-one should stop them from forming, working on and presenting a proposal to the Co-ordinating Council.
3.1.4- If two teams form for one need, so be it. their proposals will be presented to the Co-ordinating Council and one chosen. Alternatively, a compromise taking the best of both proposals may be referred back to the Work-Groups for resolution.
3.1.5- If a work-group does not spontaneously form to fulfill a perceived need, the Co-ordinating Council can call for volunteers to form said Work-Group.
3.1.6- Work-Groups will present the Co-ordination Council with proposals via their representative. They may re-present a modified proposal if for some reason the Co-ordination Council does not vote to include it in the XOOPS Project.

3.2.0- the Co-ordinating Council:
3.2.1- the Co-ordinating Council will provide all Work-Groups with a public forum, a work-group forum and a wiki page for working documents and announcements.
3.2.2- the Co-ordinating Council will consider and vote on all proposals proffered by the Work-Groups for inclusion in the project. In the case that a proposal is rejected, a written and publicly available reason will be published.
3.2.3- the Co-ordinating Council will hold public, biweekly IRC or similar chat based meetings, the minutes of which will be posted on the Co-ordinating Council's wiki page immediately after the meeting. Meetings should be open to all, but (to paraphrase Ubuntu) if it gets too noisy, the hosts are allowed to move to a private chat room. In any case, the minutes would still get published immediately at meeting's end.
3.2.4- the Co-ordinating Council meetings will have a publicly available agenda open for all to contribute to. It will be closed to contributions 48 hours before the meeting is due to begin.
3.2.5- the Co-ordinating Council will entertain all nominations for a chairperson, and will decide by super-majority (75%) vote on a chairperson with a limited term of 12 months.
3.2.6- the Co-ordinating Council Chairperson will only vote in the case of a hung ballot. His/Her role will be as arbitrator and keeper of order.

Part 4: Comments:

4.1.0- The foundation will have a clearly defined role as a workgroup with responsibility for representing the legal face of XOOPS and as the project's treasurers.
4.1.1- The site at xoops.org should provide an 'ideas box' open to the community. Ideally there should be a Work-Group attached to it to identify and report good ideas to the appropriate Work-Group if existent. The Work-Group would also introduce 'ideas box' contributors to work groups that could use their help, and in the case of original ideas that have no appropriate Work-Group in place, encourage contributors to attempt to form a new Work-Group while suggesting to the council that an idea worth considering the creation of a new work-group for, has been proposed.
4.1.2-

Illustrative Structure:

Core

Core

Modules

Themes

Security

Distributon

Creative

Graphic

Descriptive

Documentation

Core

Modules

Themes

Support

End-User Co-Ordination

Beta-Testing

Communications

News

Marketing

Site

Server Maintenance

Resource Allocation

Governance

Forum Moderation

Legal/Financial

Foundation

Click below for the code of conduct referred to in SailJapan's Proposal.

Appendix A (Code of Conduct)

Signed:

C. Moorey (sailjapan)
JAVesey
Mike (kc0maz)
Seth_sd
...