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.

An example of a happy path

1. 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.
2. You visit tiki.org and things are clear and interesting thanks to the Communications 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 Major use cases let you know that Tiki is good for your project all while having a lot more possibilities.
3. Tiki was easy to install on your platform thanks to the Packaging Team
4. Once it was installed, you had a good impression and wanted to use it thanks to the UX Team
5. You were quickly able to get a site which works for you thanks to the Profiles Team.
6. You can read up on features which interest you and learn how to configure, maintained by the Documentation Team.
7. You decide to register to tiki.org and the procedure is fun and simple, as designed by the Community Team
8. You ask some questions in the forums or in the chat room and you get some helpful responses from a member of the Community Team.
9. In the forum, you mention that there are some missing translations. A member of the Community Team points you to i18n.tiki.org and to a Tiki Local User Groups near you
10. 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
11. Every time you visit *.tiki.org, the site is up and fast, thanks to the Infrastructure Team and Performance Team
12. Because you saw it in your admin panel, you join the Newsletter, which is managed by the Communications Team
13. You find a bug and report it and someone from the Wishlist Team confirms that it is indeed a bug and assigns it to a member of the Developers Team who volunteered to maintain that feature.
14. 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.
15. This developer fixes the bug and leaves a note on the bug report asking you to test the fix on demo.tiki.org. The fix indeed works and it will be part of the next release.
16. Since you are using a Long Term Support version of Tiki, the commit is reviewed by members of the Quality Team to make sure there are no regressions.
17. A new version is released, with the bug fixed. Thanks to the Packaging Team, the upgrade was painless.
18. You think that this project is pretty cool, so you decide to make a small donation, which is managed by the Finance Team and to join your Tiki Local User Groups.
19. A few weeks later, you receive an invitation to a TikiFest in a city nearby.
20. 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 (again managed by the Finance Team).
21. Since you enjoyed meeting people at the TikiFest and all has been great so far, you decide to join one of the Teams
22. There is another release, this time to address a vulnerability. The Security Team fixes the issue and the Packaging Team again makes the upgrade seamless.
23. You are increasingly comfortable with Tiki and confident of 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 Team) to look for a developer to help build the features.
24. You become and active and long-term contributor to the project and help others have a great experience like you did.

Related

• User Type
• http://drupalladder.org/ladder/ee503327-50be-1904-8d04-9499098cad64

Alias

• Ladder of engagement
• Hierarchy of involvement
• TikiWiki Hierarchy of involvement
• Tiki Hierarchy of involvement
• Ladder of participation
• Engagement Pyramid
• Concentric Circles of Community