History: Teams
Preview of version: 157
See also:
Table of contents
Roles
Community Building
i18n
i18n Team is everything related to language strings, translations and localizations (l10n) and increase the number of languages in Tiki.
Developer
Quality
The Quality Team aims to (especially in the stable branch) to share experience and minimize the risk of introducing regression bugs or bad coding practices.
Wishlist
The Wishlist Triage Team reviews patches, bug reports and feature requests and prioritizes and categorizes them. They just triage but don't fix. They identify potential contributors and encourage them to go beyond bug reporting. Also known as task garderners. Team leader: luciash d' being 🧙
Testing
Performance
The Performance Team 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
Release
User Experience (UX) & Themes
The UX and Themes Team is responsible to make Tiki look good and be enjoyable to use for visitors and content creators, and coordinates theme development.
Configuration Profiles
Documentation
Branding
Analytics
Video Authoring
The Video Authoring Team involves everything to do with videos in Tiki, e.g. interviews, how-to instructional videos, etc..
Legal
The Legal Team handles everything to do with copyrights, licenses, etc. for content and software and helps the Tiki Software Community Association.
Fundraising
The Fundraising Team handles everything to do with donations, advertising and sponsors for the Tiki Software Community Association.
Consulting Ecosystem
Partnerships
Partnership Team 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
The 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
The Infrastructure Team is responsible for *.tiki.org hosting, server administration, domains, uptime, etc. AKA: devops, sysadmin.
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
The Finance Team handles everything to do with accounting, and managing the assets of the Tiki Software Community Association (Ex.: domain names)
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 😀.
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 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 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
- Where
- WhoWhat
- SWOT
- Model
- 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