![[Main Page]](/modules/mediawiki/images/mediawiki.png)
Contents |
Kc0maz's Proposal
Flowchart
http://www.moorey.net/images/organisational_charts/A.jpg
Introduction
Wow, I am impressed.
The passion that is expressed in this topic and several others show that the community really does care about the Xoops project.
First I applaud the foundation for providing reports. Although, I did find them woefully lacking it is much more than we had before.
First, the foundation should restrict itself to legal and financial support only. Anything else should be referred to another support team. For example, server administration should be handled by the Technical Team, not the Foundation, or the Project Council.
Second, pick a currency, any currency, either the Euro, the US Dollar, the Japanese Yen or even sea shells it doesn't matter, pick one and stick to it; it will make the accounting a whole lot easier. The financial reports should contain a balance statement, a profit / loss statement and cash flow statement. These statements combined provide a clear picture of the project's financial health. This is Accounting 101 folks, a business basic.
I know, this is not a business, it is an open source project, and I agree, up to the point we start dealing with money, then we should be all business.
I am going to go over my take on some different areas.
Project Manager
The Project Manager should not be a member or team leader of any other team. He is to guide the various teams toward a common goal (vision statement) and work to properly equip each team with the tools they need to preform their function. Other than the Technical Team, The Project Manager should be the only one with full administrative rights to Xoop.org. Not to use, rather to grant those rights to the various teams.
The Project Manager should be selected by a popular vote in this manner: - A committee of three to five people select three to five qualified candidates The committee members should:
- Be an active community member in good standing
- Not be a Team Leader
- Not be a member of the foundation
- Be selected by the project council & Foundation board
- Once the names are announced, there could be a one or two week discussion period - Followed by a 48 hour voting period - Once the committee reviews and certifies the results, they are to be published - The new Project Manager takes over on the first of the next month - The community Thanks the committee for their hard work
The Project Manager would hold the position for 18 months, and can be select for two consecutive terms.
Project Council
The Project Council should be the focal point of coordination. This is where team leaders work together toward the common goal (vision statement) Each member of the project council should have a purpose. Some one should not be added because they 'good person to have on board.' The Project Council can create or dissolve teams as needed. The Project Council should be comprised of-
- The Project Manager
- One member from the Foundation
- The team leaders from both the 'Project' and 'Community'
- Local Support Coordinator
The Teams should be created to preform some kind of function. None of this team to be a team stuff. To be a team, a group must be comprised of three or more people. Each team select its own leader, and sets it own rules. Each team MUST respect each other anonymity, in other words your team does its job and let the other teams do their's. Here is a list of teams and their basic function. This list is not inclusive. Feel free to add any I may have missed.
Core development
Core development Like the name implies, they work on the Xoops CMS core. When they have a new version to be tested or released, they work with the council to get that done. They also maintain the core repository
Module development
Module development[i] Sets and maintains the standard for modules. They evaluate and certify new modules and updated modules. They maintain the module repository.
Themes development
[i]Themes development Sets and maintains the standard for themes They evaluate and certify new themes. They maintain the theme library. They also maintain the 'official' Xoops.org theme
Documentation
Documentation team creates and maintains 'official' documentation for the Xoops core and core modules. Works with other teams to create user manuals and tutorials as needed. They also maintain the FAQ
Marketing
Marketing team formally know as the communication team or news team This team produces news items, and promotes Xoops on other sites. They also collect first and second tier survey results and feeds it back to the module or core development teams. The development teams need to know what features the end user is looking for. In addition they assist in creating advertisements and the Xoops.org home page.
Community Coordinators
Community Coordinators provide the one on one customer service. They direct people to the correct area of the documentation or correct area for assistance. They also moderate the user forums, comments, and maintain the user database. They are the first 'human' contact that an end-user has with the project.
Conclusion
Here is how I envision the teams work together: The core development announces to the council they have the next version ready for release. The documentation team prepares / updates any documentation. The Community Coordinators reviews any known issues brought up by the beta testing. The Marketing team prepare and releases news articles and press releases.
I like the Xoopsinfo forum structure. I would like to mirror that on Xoops.org for the various teams. (yes, Damaster, I am plagiarizing) by having a public forum, a work forum, and a private forum makes good sense.
I don't have the corner on good ideas, I never claimed I did. I depend on the community to present their ideas and maybe they can be worked fabric of the Xoops project.
With all of this in mind we still need: - A vision statement – where are we going - A mission statement – how are we going to get there - The rest of the teams need to be formed
One last note: All of this is garbage, unless the community is willing to step up an take some responsibility.
