The following personas are fictional characters that we defined in order to represent the different types of users that might use Kyma. Keep these personas in mind when contributing to Kyma as they will help you to understand Kyma users' needs and goals (GAINS 💚) and major pain points (PAINS 💔).
Name | Matthew |
Age | 26 |
Occupation | Cloud-Native Engineer at PureJoy |
Characteristics | Open source enthusiast and contributor. You will meet him at the webinars and community meetups. |
Kubernetes experience (1-6) | 📖 📖 📖 📖 📖 📖 |
Accountability/Decisiveness (1-6) | 💪 💪 |
Slogans | Is there a CLI for that? Can I automate it? |
- 💚 I want to write my Kubernetes application using my favorite IDE and store it in GitHub.
- 💚 I want to build Kubernetes applications in any language, really fast.
- 💚 I need a thin "multi-cloud" runtime for my application.
- 💚 I need a super easy, automated deployment directly from my application's source code.
- 💚 Help me understand Kyma API.
- 💔 I hate doing backward engineering in order to understand how things work together.
- 💔 Don't make me use code editors on the web.
- 💔 I don't want to be locked with any tools. Let me replace or completely opt out of any of the preconfigured components.
- 💔 I hate tons of configuration.
Name | Sebastian |
Age | 38 |
Occupation | Enterprise Architect at PureJoy |
Characteristics | Sebastian wants to bring innovation to products developed at PureJoy. He understands the needs of his organization and seeks for solutions in the CNCF landscape. He evaluates CNCF projects to identify what those tools bring for free and what the gaps that need to be implemented by the teams in his organization are. He needs to convince his bosses and his development team to new solutions and he is accountable for his recommendations. |
Kubernetes experience (1-6) | 📖 📖 📖 📖 |
Accountability/Decisiveness (1-6) | 💪 💪 💪 💪 💪 💪 |
Slogans | I know what I want... not yet sure how to achieve it. |
- 💚 I need to evaluate Kyma fast (within 1 day).
- 💚 I love tutorials, sample code, recipes that refer to my use cases (i.e authentication/authorization flows).
- 💚 I want to ensure product (industry) standards for free (i.e security, accessibility, observability, tracing, etc).
- 💚 I want a futureproof platform, based on references.
- 💚 With Kyma, I want to connect to systems I know (public and internal ones).
- 💚 I need a trial version of Kyma before I can recommend it.
- 💚 I need agility in architecture design. I want to replace individual modules if needed.
- 💚 I want a painless upgrade path.
- 💚 I want operational support.
- 💔 I give up on a project if success stories and/or references are missing.
- 💔 I give up on a project if documentation (incl. tutorials) is missing.
- 💔 I don't want to take extra care of security, monitoring, tracing, etc.