Loading...
 

Roles and Teams

See also:


Thinking about participating? Talk to us on IRC.

Roles

Community Building

Community Building 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.

i18n

Internationalization is everything related to language strings, translations and localizations (l10n) and increase the number of languages in Tiki.

Developer

The Developers are the umbrella group responsible to make Tiki better as an application. Please see how to get commit access.


Quality

Code Review aims to (especially in the stable branch) to share experience and minimize the risk of introducing regression bugs or bad coding practices.

Wishlist

Wishlist Triage reviews patches, bug reports and feature requests and prioritizes and categorizes them. They just triage but don't fix.

Testing

Testing focuses on functional, unit tests, as well as front-end testing to catch bugs early and to keep the quality high.

Performance

Performance is interested in high-performance and high availability of Tiki. Tiki should not cause performance bottlenecks on shared hosting, should have options to allow it to be used in highly scalable clustered environments, and high-availability configurations.

Packaging

Packaging involves making Tiki easily deployable on various platforms and 1-click installers.

Release

Release is about managing the process to achieve timely releases of Tiki, and coordinating throughout the community as almost all Roles and Teams should participate actively to each release. A balance needs to be maintained: "Don't rush, yet don't slow down". See all the Release Roles.

User Experience (UX) & Themes

UX and Themes is responsible to make Tiki look good and be enjoyable to use for visitors and content creators, and coordinates theme development.

Configuration Profiles

Configuration Profiles are 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.

Documentation

Documentation has the challenge of maintaining documentation for what Tiki does, hundreds of features, over 1000 pages, and a new release every 6 months!

Branding

Branding involves market analysis, brand management and providing community tools for a coherent and efficient message.

Analytics

Analytics is responsible for everything to do with stats, big data, etc. both in Tiki the software and Tiki as a community.

Video Authoring

Video Authoring involves everything to do with videos in Tiki, e.g. interviews, how-to instructional videos, etc..


The Legal Team handles everything to do with copyrights, licenses, etc. for content and software and helps the Tiki Software Community Association.

Fundraising

Fundraising handles everything to do with donations, advertising and sponsors for the Tiki Software Community Association.

Consulting Ecosystem

Consulting Ecosystem is all about fostering healthy growth of the network of companies that conduct business using/around Tiki, 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 meet their needs.


Partnerships

Partnerships are needed to foster communication and collaboration with other organizations.

Welcoming New Users

Welcoming New Users is all about helping new users make good use of Tiki once it 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 better new user orientation is increasing the number of Tiki users which should see an increase in developers.

Teams

Communications Team

Communications Team is responsible primarily for our external message (press releases, newsletters, social media, etc.)

Branding vs communications vs community building

We recently spun off Branding from Communications Team as a separate role. There is also an overlap with Community Building. The following table provides some insight on the differences.

Publishing official News about Tiki Communications Team
Our official presence on Twitter, Facebook, etc. Communications Team
Generally promoting Tiki on social media Community Building
Posting articles about Tiki on your own blog/site Community Building
For people to have a good impression when they visit Branding
For people to understand what we do Branding
Developing a style guide for visual and textual communication Branding
To have lots of traffic and good SEO Communications Team can coordinate but everyone can help

Infrastructure Team

Infrastructure Team is responsible for *.tiki.org hosting, server administration, domains, uptime, etc.

Security Team

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.

Finance Team

Finance Team handles everything to do with accounting and administration for the Tiki Software Community Association.

Tiki Admin Group

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

Future separate roles

In the future, we'll perhaps split up certain roles to provide a finer granularity.

  • Events (for now, covered by Community Building)
    • 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 Maintainers: 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 the review of feature requests and bug reports, keep docs up to date and make sure the community is dogfooding (when relevant).
  • Sub-teams for Developers 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
    • Why
      • 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.

Related

Alias

Why Register?

Register at tiki.org and you'll be able to use it at any *.tiki.org site, thanks to the InterTiki feature. A valid email address is required to receive site notifications and occasional newsletters. You can opt out of these items at any time.