On this page, we'll make something like Maslow's hierarchy of needs but for the evolution of participation to the Tiki community. Think of it of a hierarchy of involvement. It could also be seen as Concentric Circles of Community or an Engagement Pyramid
The goal for the community is to have strategies and tools for as many people as possible to become more & more active in the community. The strategy is quite different for someone to migrate from Web user to Tiki user than from Inactive developer/contributor to Occasional committer/contributor.
It is normal for people to come & go, so we must have a constant flux of new people in the project and get them involved as much as possible.
- You learn about Tiki because of the work of the Communications Team. You had seen powered by Tiki before but this recent article on a news site made you want to explore more.
- You visit info.tiki.org and things are clear and interesting thanks to the Branding Team and you decide to try it out. You have a project in mind and the site clearly caters to your needs. The descriptions of the use cases let you know that Tiki is good for your project all while having a lot more possibilities.
- Tiki was easy to install on your platform thanks to the Packaging Team
- Once it was installed, you had a good impression and wanted to use it thanks to the UX and Themes Team
- You were quickly able to get a site which works for you thanks to the Configuration Profiles Team.
- You can read up on features which interest you and learn how to configure, maintained by the Documentation Team.
- You decide to register to tiki.org and the procedure is fun and simple, as designed by the Community Building Team
- You ask some questions in the forums or in the chat room and you get some helpful responses from a member of the Community Building Team.
- In the forum, you mention that there are some missing translations. A member of the Community Building Team points you to i18n.tiki.org and to a Tiki Local User Groups near you
- You decide to contribute a few translations on i18n.tiki.org, which are committed to the main code base by someone in the i18n Team
- Every time you visit *.tiki.org, the site is up and fast, thanks to the Infrastructure Team and Performance Team
- Because you saw it in your admin panel, you join the Newsletter, which is managed by the Communications Team
- You find a bug and report it and someone from the Wishlist Triage Team confirms that it is indeed a bug and assigns it to a member of the Developers Team who volunteered to maintain that feature.
- You see a typo in the documentation and you fix it. A member of the Documentation Team sends you a private message to thank you.
- This developer fixes the bug and leaves a note on the bug report asking you to test the fix on show.tiki.org (which is managed by the Infrastructure Team and Wishlist Triage Team. The fix indeed works and it will be part of the next release.
- A new version is released, with the bug fixed. Thanks to the Packaging Team, the upgrade was painless.
- You think that this project is pretty cool, so you decide to make a donation, which is managed by the Fundraising Team and to join your Tiki Local User Groups.
- A few weeks later, you receive an invitation to a TikiFest in a city nearby, sent by the Community Building Team.
- You have a new idea for a website, so you decide to get a new hosting plan. You use the affiliate link so this provides another donation to the Tiki Association.
- The Finance Team makes sure the funds are well tracked and managed.
- Since you enjoyed meeting people at the TikiFest and all has been great so far, you decide to join one of the Teams
- There is another release, this time to address a vulnerability. The Security Team fixes the issue and the Packaging Team again makes the upgrade painless.
- You are increasingly comfortable with Tiki and confident in it as a platform. You contemplate an even bigger web project but if it goes through, you will want additional features. So you check out the list of Consultants (managed by the Consulting Ecosystem Team) to look for a developer to help build the features.
- You become an active and long-term contributor to the project and help others have a great experience like you did.
- Use cases