This page is a constant work in progress and provides an overview of who is doing what in the Tiki community. This is not a top-down directive or anything, but rather a collaborative list to enable all in the community to work more effectively together.

Many contributors might still be missing from this list... please help to make this page better!

1. Introduction

Tiki Wiki CMS Groupware is a vast project. It's tricky for new people to know how the Tiki Community is organized to find the right person to contact to start to contribute. Newcomers often ask:

• What may I expect from others within Tiki Community
• What do others expect from me?
• Who does what?
• Who should I talk to? How does it work?

This page is intended to help answer these question.

Important: Everyone is a volunteer. Things get done because someone like you decides to take the time to make it better.

Tiki is a free and open source software project. Anyone can join and participate in the Tiki Community without paying or officially joining anything — simply register.

If you are new to open source, a good place to learn more about how open source software communities work is to read about it on Wikipedia.

Ready to Participate?

2. Project Administrators

2.1. What

The Tiki Admin Group is responsible for governance, overall coordination and all the rest including whatever that might fall between the cracks 😀.

2.2. Who

• Marc Laporte
• Sylvie Gréverend - php developer, architect
• luciash d' being
• Oliver Hertel
• Xavier de Pedro - teacher, researcher and a bit of architect
• Gary Cunningham-Lee - theme integrator, designer, misc.
• Nelson Ko
• Pascal Kustner (pkdille)
• Rick Sapir (ricks99) - User Interface, marketing, Tiki for Dummies Smarties, Tiki Essentials
• Jonny Bradley WYSIWYG, jQuery
• Changi67 | Infrastructure Team, Packaging Team
• Jean-Marc Libs (jyhem)
• Rodrigo Sampaio Primo Brazilian translation, MediaWiki to Tiki importer

Private discussion list: admin at tiki.org

3. Elders

3.1. What

Individuals who have provided outstanding contribution to the project (usually ex-admins which have become inactive or are still active but prefer not to be formally in the admin group) and are consulted for important decisions. A bit like "Past presidents" in some non profits.

3.2. Who

• mose
• Florian Gleixner
• Luis Argerich (founder). You can learn more about him here and here
• Patrice Weber (nyloth) File Gallery, Calendar, SVN, release management, etc. (most of the code really)

Elders can still be on the admin at tiki.org list

4. Security Team

4.1. What

The Security Team is a trusted group. This team is responsible to review security reports and to proceed to a pro-active audit at each major release. Security Team members are added by vote by the Admins following recommendations of current members.
http://security.tiki.org

4.2. Who

The security team is a small group of core developers and security consultants who volunteer their time to proactively promote security through testing and education, as well as respond to vulnerability reports received from external security analysts.

5. Developers

5.1. What

To reach "everyone":
tikiwiki-devel@lists.sourceforge.net.

5.2. Who

This is an incomplete list.
http://www.ohloh.net/p/tikiwiki/contributors

6. Consultants

To identity a Tiki Consultant/Service Provider that you can hire to help you with various aspects of Tiki usage please see: Consultants

7. All Roles

Please find out more about various Roles: Community, Infrastructure, i18n, Developer, Quality, Wishlist, Testing, Security, Performance, Packaging, User Experience (UX) & Themes, Profiles, Documentation, Communications, Branding, Legal, Finance, Fundraising, Consulting, Partnership, Admins

8. Designated Role Coordinators

Tiki believes in the power of self-organization and is *not* a top down organization. While it is recognized any person helps out from time to time in coordinating activities related to Roles, certain individuals may from time to time be designated by the Tiki Admin Group as Role Coordinators. Obviously, these individuals would have shown their commitment to Tiki by contributing actively and exhibiting leadership in the various Roles, and are currently active in those Roles, but the main purpose of such designations are to facilitate such leaders in their communication with other organizations to provide a level of officialness with regards "who they are" in the community.

Not all roles need to have designated coordinators. Roles that interact more with external parties tend to require it more. If you feel that you need to be on this list in order to perform a role effectively, e.g. to communicate who you are to other organizations, please let the Tiki Admin Group know.

List of everyone who has contributed code

Please see: List of all code contributors

Page aliases

• Who
• What