Teams
What teams are- A way to regroup smaller groups of individuals towards more focused goals, according to their experience, availability & interests. To make our community more efficient and scalable.
- They are mentors, coordinators, facilitators.
- A way to make it easier to get involved
- A way to deal with information overload.
- They are waiting for you to join!
- Self-organizing
- Dogfooding the Organic Groups, Group Watch, PluginInvite, PluginMemberList and PluginSubscribeGroups features.
- They are called teams and not groups 1- To avoid potential confusion with group feature and 2- To express that these Teams have things to do!
What teams are not
- They are not closed. Each team should have as many people as possible.
- Are not putting strict limits of responsability, as there is a lot of collaboration/overlap between mandates.
- These people are not gatekeepers. The community is wiki way! You don't have to ask permission to commit code or improve the documentation for example. We don't want any potential bottlenecks. It doesn't mean that these people are "responsible" to help you. They are volunteers just like you.
What teams should do
Maintain their wiki page which answers:
- What? Why? Who? When? How? etc.
- What is on the todo list? (so everyone can hop in and help)
- What are the responsibilities at each release? Release Roles
- Short term tasks
- What are the ongoing responsibilities? (For long-term contributors)
- Medium and long term projects
- Links to procedures and best practices.
Table of contents
Community
The Community Team focuses on making Tiki better as a community, and coordinates all efforts related to user support, volunteers coordination, welcoming new users, TikiFests, Dogfood, etc.Infrastructure
The Infrastructure Team is responsible for hosting, server administration, domains, uptime, etci18n
The i18n Team is responsible for everything related to language strings, translations and localizations (l10n) and increase the number of languages in Tiki.Developer
The Developer Team is the umbrella group responsible to make Tiki better as an application. Please see how to get commit access.There are 300 members.
This is an open group. Anyone can join (just click that button!). These people are or were very involved with Tiki. They can be good guides to get you participating in fixing or improving something in Tiki. If they don't know the answer they probably know who to ask for help. Tiki is a vast project and no one can realistically need all features. Thus some people are more specialized in certain areas. You should add on your UserPage what your specific area of interest/expertise is.
Quality
The Quality Team reviews commits in the stable branch to share experience and minimize the risk of introducing regression bugs or bad coding practices.Wishlist & testing
The Wishlist Team reviews patches, bug reports and feature requests and prioritizes and categorizes them. They just triage but don't fix.Security
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.Packaging
The Packaging Team is responsible to make Tiki easily deployable on various platforms and Auto-installersUser Interface (UI) & Themes
The UI Team is responsible to make Tiki look good and be easy to use. The UI team also coordinates theme development.Documentation
The Documentation Team (aka Editorial Board) has the challenge of maintaining documentation for what Tiki does, hundreds of features, over 1000 pages, and a new release every 6 months!Meetings:
The Editorial board meets occasionally, to discus mainly issues of standardizing documentation and general best practices and improving findability of stuff.
See Editorial Board on Doc.tikiwiki.
Profiles
The Profiles Team is responsible to maintain the featured profiles and to assist contributors of community profiles, to produce a great first impression and useful out-of-the box solutions.Communications
The Communications Team is responsible to inform, explain, promote Tiki the application and Tiki the community, to attract more & more users & contributors.Legal
The Legal Team handles everything to do with copyrights, licenses, etc. for content and software and helps the Tiki Software Community Association.Please contact an Admins Team member to join this team.
Admins
The Admins Team is responsible for governance, overall coordination and all the rest that falls between the cracks
. See: WhoWhatFuture teams
In the future, we'll make more- Feature teams: team that is pushing a specific feature (ex.: Trackers, or File Galleries, etc. see Keywords or Merge categories on dev.tiki.org a bit like "maintainers" in some software. They should take initative for review of feature requests and bug reports, keep docs up to date and making sure the community is dogfooding (when relevant).
- Sub-teams for developer team for major features and other aspects
- Tests
- Performance
- etc
- Financial / foundation, which is now handled by the Admins Team.
Related
- Where
- WhoWhat
- SWOT
- Model
- http://developers.slashdot.org/story/12/03/12/1728234/how-to-contribute-to-open-source-without-being-a-programming-rock-star
.
, 00:16 CEST, Fri 18 May 2012:
oops Marc postponed to Friday 18th of May and then always at the third Friday
, 13:07 CET, Fri 16 Mar. 2012:
What happened to the BBB room ?