[1pt][E4] As a chair of OS Cimate I want to define a user journey path, so I can hand it over to the dashoard/metrics area.

[schwesig]

• [ ] defining a user journey for OS Climate

1pt is defined as one day

[hemajv]

@erikerlandson do let us know what parts of the user journey we should focus on and we can start fetching the relevant data for it.

Some of the user actions/events we could track based on user acquisition and user engagement:

User Acquisition

• input (entry point for the user): User creates on-boarding request output a: user creates an on-boarding request output b: user joins Slack channel

User Engagement

• input (entry point for the user): User creates an on-boarding request to the project output a: user logs into the OS climate cluster (can fetch user information from Prometheus?) output b: user creates an issue in the repo output c: user creates a PR output d: user reviews a PR

[erikerlandson]

@hemajv I think what you have above is a great start!

There is no one community meeting where meeting attendance is tracked, so I'm unsure if there is any "input" on the User Acquisition side. "Creates onboarding request" is probably the most consistently observable entry point.

Other github events that might be useful:

• creates new repository under os-climate gh org

Stretch goals:

• gh user who is osc member also submits issue or pr against gh://operate-first/apps (or odh-manifests, or support)
• track queries submitted (or just frequency of queries, or first query) by same users in trino (if this can be extracted from the trino dashboard telemetry)
• detect long intervals when "no tracked events" happen

[hemajv]

thanks for the input @erikerlandson, we will look into how best we can capture these :+1: