Tiki Teams are small groups of individuals towards more focused goals, according to their experience, availability & interests.
Table of contents
- User Experience (UX) & Themes
- Discussion about branding vs communication
- Discussion about split of this page
- Future teams
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, Webinars, Dogfood, etc. The coordinator is Torsten Fabricius.
The i18n Team is responsible for everything related to language strings, translations and localizations (l10n) and increase the number of languages in Tiki. The coordinator is Olaf-Michael Stefanov (omstefanov).
You are not currently a member of this team. Should you wish to join the 21 members in this team and contribute to its work, you need to be logged in. When you are logged in you will see a link below, which you can use to join the team.
There are over 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.
The Quality Team reviews commits in the stable branch to share experience and minimize the risk of introducing regression bugs or bad coding practices. We are looking for a coordinator for this team. Please contact Nelson Ko, CC Marc Laporte and Pascal St-Jean if you can take the lead on this.
The Wishlist Team reviews patches, bug reports and feature requests and prioritizes and categorizes them. They just triage but don't fix. The coordinator is Pascal St-Jean.
The Testing Team focuses on functional and unit tests to catch bugs early and to keep the quality high. The coordinator is Alain Désilets.
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. The coordinator is Pete Jalajas (whom you can contact to join the team).
The Performance Team is interested in high-performance and high availability of Tiki. Tiki should not cause performance bottlenecks on shared hosting. The coordinator is Marc Laporte.
The Release Team is responsible for timely releases of Tiki, and coordinating throughout the community as almost all teams should participate actively to each release. In an ideal world, where all teams are functional and everything is kept up to date, the release team has an easy job. However, if another team has trouble, it often ends up becoming a blocker for a release. Thus, the better the teams work year-long, the smoother the release process is. "Don't rush, don't slow down". See all the Release Roles. The coordinator is Bernard Sfez.
The Bootstrap Team has the task to implement the "Twitter Bootstrap" design framework into Tiki as a replacement for Tikis Classic Layout
Next major coding steps in November 2013 at the TikiFestBootstrap in Canada.
User Experience (UX) & Themes
The UX Team is responsible to make Tiki look good and be enjoyable to use for visitors and content creators. The UX team also coordinates theme development. The coordinators are Gary Cunningham-Lee and luci aka luciash d' being
The Profiles Team is responsible to produce a great first impression and useful out-of-the box solutions for site admins. Maintaining profiles for use cases, a coherent admin panel, and sensible defaults. The coordinator is Greg Wheat.
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! The coordinator is Olivier (pianolivier)
The Communications Team is responsible primarily for our external message (press releases, newsletters, social media, etc.) The coordinator is Rick Sapir.
The Branding Team is responsible for market analysis, brand management and providing community tools for a coherent and efficient message.
The Analytics team is responsible for everything to do with stats, big data, etc. both in Tiki the software and Tiki as a community. The coordinator is Pascal St-Jean.
The Video Team is responsible for everything to do with videos in Tiki.
The Legal Team handles everything to do with copyrights, licenses, etc. for content and software and helps the Tiki Software Community Association. The coordinator is Nelson Ko (whom you can contact to join the team).
The Finance Team handles everything to do with accounting and administration for the Tiki Software Community Association. Please contact Nelson Ko, CC Marc Laporte and Pascal St-Jean if you can take the lead on this.
The Fundraising Team handles everything to do with donations, advertising and sponsors for the Tiki Software Community Association. We are looking for a coordinator for this team. Please contact Pascal St-Jean, CC Marc Laporte & Nelson Ko if you can take the lead on this.
The Consulting Team is responsible for fostering the development of the Tiki consulting ecosystem, which includes increasing the number of full-time Tiki consultants and making it easier for potential Tiki users to find the right consultants / service providers in the Tiki community to suit their needs.
The Partnership Team is responsible to foster communication and collaboration with other organizations. The coordinator is Pascal St-Jean.
The Admins Team is responsible for governance, overall coordination and all the rest that falls between the cracks . The group was previously known as TAG (Tiki Admin Group)
The Retention Team is responsible for increasing new user retention once Tiki has been downloaded.
The belief is that Tiki can be very intimidating for new users, and though many people may download it, the impression is that a large portion of them give up before really seeing the potential behind it.
The end-result of increasing retention is increasing the number of Tiki users which should see an increase in developers.
Discussion about branding vs communication
|News about Tiki on another site||Communications|
|Our presence on Twitter, Facebook, etc.||Communications|
|For people to have a good impression when they visit||Branding|
|For people to understand what we do||Branding|
|To have lots of traffic and good SEO||?|
Discussion about split of this page
Perhaps it would make sense to split:
Tiki, the Software
-- -- --
User Experience (UX) & Themes
Tiki, the community
-- -- ---
Debatable, Both or n/a
In the future, we'll perhaps make more
- Events team (for now, covered by Community Team)
- Organize events, foster local events and make sure Tiki is present in major events
- Webinar events. Occasionally there are special webinars involving multiple presenters. Coordinating such events by making sure all the elements (power point, chat room animation, etc) are set and ready on time for the event.
- Feature teams: team that is pushing a specific Use Case and/or 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 initiative 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 Developers Team for major features and other aspects
- Should it be split by front-end and back-end? Or by use cases?
- Advisory board: https://en.wikipedia.org/wiki/Advisory_board
- Who: These people are from outside the community. They are individuals with a history and credibility in our field (ex.: Dirk Riehle or Karl Fogel)
- What: They provide advice but do not participate in the day to day activities
- We want their advice, contacts and credibility
- They want to help a project which they feel is important
- Most of the what happens at Tiki is public. But there a few aspects (legal, financial and partnerships) that are not. The advisory board will have access to everything.
- 14 Ways to Contribute to Open Source without Being a Programming Genius or a Rock Star
- How To Contribute To Open Source without Being a Programming Rock Star