We will review the main aspects of the Tiki project including the Community and its management.
It is based on 20 years of consultancy as well as my work on the Tiki software project.

• What is the Tiki project
• Tiki features out-of-the-box
• Tiki options and management tools
• Overview of the Tiki Software
• Pros and cons about the Tiki software
• How to discover more about the Tiki software ?
• The Tiki community and association model
• The technical decisions and development
• Some facts and links about the Tiki Software development

The mission of the Tiki Software Community Association is to foster the development of the free and Open Source software, Tiki Wiki CMS Groupware, and to promote the free use of this software by all who can benefit, particularly individuals, groups, and organizations for whom online collaboration will strengthen their communities and facilitate achieving their goals together.

In essence the Tiki project is made of:

• A software
• A collegial leaded association (Project admins)
• A coders collaborative efforts (Developers)
• An Open Source community (Users, Developers and Admins)

Tiki is an all-in-one solution (no 3rd party plugin), it is coded to allow interaction between features and options.
It can be deployed on a local intranet or internet (online or offline) and allow quick publishing. Tiki allow fine tuning its features or heavy customisation and comes with ready to use solutions for:

Running features together require multiple and flexible components to control interoperability.
Tiki comes with a long list of System preferences and Security preferences (and tools) but also with a Users and Content management tools as well as a complete Multilingual and Translation feature.

Tiki is a no-code/low-code web framework allowing high level of customization able to interact directly with database values through the Tiki Trackers. Trackers allow the users to built database access through defined type fields and distribute all this data to most of the others Tiki features. Types are various like text, date, list, files and category field as well as relational fields (itemlink, itemList, username, user preferences, etc.) and advanced like Mathematical and Mailbox.
Dedicated plugins with templates, filters and paginations tools allows to configure multilingual user interfaces and visual enhancement.
Import and Export advanced tools allows third party data acquisition and the process can be even automatised internally using the Scheduler functionality.

Combining Trackers and the wiki makes Tiki a Structured Wiki software.

This is about the Tiki project, more information on the open source model here.
What people say or think

This is a very short presentation and you may want to find more information:

• Tiki Wiki the website builder
• Tiki Official site - the software
• Download Tiki
• Documentation
• Video Tutorials
• Tiki versions

The Tiki model is based on DO-Ocracy !
If you do, you act or you contribute to the project, your voice will count as equal as anyone else.

In that regard, there is no limitation to join the developer team and start to commit code, add translations, participate to the documentation, create profiles, join the meetings, etc.
To protect everyone interest, there are guideline based on 3 simple rules:

• Respect the Environment (think about other users)
• Commit early, Commit often (allow other to review and prepare)
• Make it Optional (don't change existing behavior)

Those rules are extended through development guidelines (editable by anyone) and open discussions held by and with the user community
Monthly Roundtable meetings, Tikifeast (regular international meeting), XMPP chat (Tiki feature), forums and users maillist.

Among the Tiki teams, a dozens of admins manage the legal or financial aspect of the project and the infra-structure during TAG meetings.

As seen, there are many options for an individual or a company to influence the code and the "next" features.
Those are the typical motivation type for a change in the code change:

• Improvement in existing technologies (PHP8, BS4 to BS5)
• Change of standards (devices, users expectations, etc)
• Feature addition by a coder (owner)
• Feature addition for a project (3rd party request)
• Maintenance of the software (security, translation, upgrade)
• Abandoned feature, technology or 3rd party project.
• Change in licensing of 3rd party component (ElasticSearch to Manticore)

There are specific development that are not part of the code and just added to a local project or profile.

Another interesting point and somehow different of many project, Tiki is a "eat your own dogfood" project.

Links of interest about Tiki development:

• https://tiki.org/Versions
• https://tiki.org/DogFood
• https://dev.tiki.org/Development

• Contact me for additional information