helm-charts VS orbit-model

Examples: Netlify has an entire Integrations Engineering team. Currently it just works on Next.js integrations, but it could also own, for example, the VS Code extension. In the past I helped build out Netlify Dev and react-netlify-identity as part of this function. Popular quick start tooling like Docker Compose and Helm Charts also fall under this function.

Even though the migration was prototyped with a self hosted cluster of Temporal (using our Kubernetes helm chart), they decided to sign up for Temporal Cloud as an early design partner. As a small startup, they didn't want to manage Temporal themselves. "We migrated progressively using feature flags, and verified performance as we went, but we had confidence in the Temporal team so we didn't stress about load testing."

I've been working in Developer Relations now going on 5 years and I've seen a lot of attempts to measure the activities of DevRel teams. There is often a lot of ambiguity about how best to measure the work that DevRel does. Do you utilize the AAARRRP model from Phil Leggetter, the Orbit Model from the Orbit team, the traditional sales funnel or something else?

The Orbit Model community framework, around which Orbit is built, is an interesting read too: https://github.com/orbit-love/orbit-model

Number of Orbit level 1 users

It was not long before Orbit became visible on our radar. It promised not only a useful platform to deepen understanding of the community. It put forth an entirely new conceptualization of community-building. In fact, the platform -- the product -- only came after the ideation and thoughtful work of crafting the Orbit Model. Deliberate systematized methodologies don't usually take precedence in emerging start-ups. This was something different.

What is community love? We’re still big fans of Orbit’s definition for it. Love is a member's level of engagement and investment in the community. Someone with high love is highly active and plays key roles in the community, like contributing, moderating, and organizing.

I would strongly recommend thinking about other activities that your community members may take that is not tracked in Orbit. For example, newsletter or blog subscriptions. You can use Zapier to integrate activities from other tools, like your subscribers—which is a pretty highly weighted activity in my book. If you didn't catch that weighted reference, head back to the Orbit Model docs.

[2] https://orbit.love/blog/why-orbit-is-better-than-funnel-for-...

"Characterizing the developer journey as a linear funnel doesn’t really tell the whole story, as it’s essentially scoped to awareness and conversation — the journey is much more complex. I think onboarding to the community itself, retaining over time, and advocating for others to join, is a huge part of the journey... In this world, you want to understand how folks are engaging with the community as well as with the company/product, with product metrics (activation, adoption, etc) existing as second-order effects of the community. The Orbit Model, versus the funnel, tries to tell this nonlinear and comprehensive story."

To understand what Orbit as a platform is, it's important to first understand what Orbit as a _model _ is. The Orbit Model is a framework for building high gravity communities. A high gravity community is one that excels at attracting and retaining members by providing an outstanding member experience.

Re: your question in the post title I'd say yes, report to marketing because in the end the person(s) work on content and events - both marketing activities. You should also treat this person more like a product marketer where the metrics aren't black and white like those of a growth marketer. If you want to assign metrics as goals for someone in this role, this may give you some ideas: https://github.com/orbit-love/orbit-model. I don't want to assign lead number to a DevRel person.