On this page, we'll make something like Maslow's hierarchy of needs but for the Tiki community.
We'll make a list of roles relative to Tiki. Think of it of a hierarchy of involvement. It could also be seen as Concentric Circles of Community
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.
Related: User Type
Non-Web user
Nothing we can do 😊
Web user
Would be good to have subtle & clean self-promotion links/banners/etc. on Tiki-powered sites.
Communications Team with Viral Tiki
Someone with a web project
Needs to pick a tool.
Communications Team to explain when/why Tiki is a good choice.
Tiki user
Nice UI, good documentation, reliability
Community Team to help user make project a success.
Tiki admin
Promotion within the app
Inactive developer/contributor
Good community & call to action
Occasional committer/contributor
Good community / call to action / mentoring & Commercial ecosystem
Active Developer/contributor
Directly asking this person to do more & Commercial ecosystem
Active team member
- We are currently working to improve team structure & Commercial ecosystem
Project Admin
Commercial ecosystem
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
- You learn about Tiki because of the work of the Communications Team
- You visit tiki.org and things are clear and interesting thanks to the Communications Team and you decide to try it out
- 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 Team
- You were quickly able to get a site which works for you thanks to the 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 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 Team.
- In the forum, you mention that there are some missing translations. A member of the Community Team points you to i18n.tiki.organd 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
- 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 Developer 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 not 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.
- 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 small donation, which is managed by the Finance Team.
Alias
;){kind=link}
;){kind=link}