Markdown was the inspiration: easy to scan, consistent, doesn't support fluff, etc. Trying to avoid many of the typical SaaS site tropes that get in the way.
Oh, my bad, thought you meant it was built in markdown, like MDX or something.
I wish you could do all this in plain markdown; putting things side-by-side in a github readme can be tricky. Have to resort to sub/superscript hacks just to make image captions.
Thanks for the mention. We have been chatting with maintainers this past year and recommend new contributors as the best metric to start identifying repo health.
Another example is the rate of selection, how many contributors outside the core team or employees.
We plan to expose more metrics like these in app really soon.
I can confirm that it's not a paid promotion. Just my reflections on what I see as being exemplary community work.
Sorry to hear you found reading the article difficult. It's an aesthetic choice I've received only positive comments about before this, but I'll look into providing some option to disable it - perhaps I could hook into the
prefers-reduced-motion option or similar.
Not astroturfing, just my take - I have no connection to the company. There's a section that goes into the licensing change a little more, but in my view, there's a lot of great stuff that can be learned from HashiCorp's approach to community from before the licensing change that is worth knowing about. If anything it highlights just what they've put at stake by making that move.
No, it's new, although was completed a couple of days before their announcement and updated to reference it. My audience is primarily community managers, DevRel, and community-minded rev teams and HashiCorp have done an exemplary job at community-led until the licensing change. There's a lot such folks can learn from before the licensing change, I didn't want to wipe that away. Also, I didn't see it as my place to provide too much commentary on it specifically, since the impact isn't yet fully understood.
>HashiCorp have done an exemplary job at community-led until the licensing change
Have they? Obviously, part of this should be taking care of yourself, and HashiCorp wasn't exactly profitable. It could be argued they didn't monetize the right things, and that led to a bad desperation move.
If you read article it outlines why I think so. Profitability is a larger issue than their community programs. Although, the process of converting community into customers is still slow for them, which I think is a contributing factor for sure.
Asking around, some of the agents being worked on by folks I know include agents that:
- auto-update issue statuses based on GitHub activity.
- post daily summaries of Linear changes to Slack.
- discusses product requirements with you and creates Linear issues
- listens to Sentry error stream and auto creates linear issues for new crash signatures
- interprets GitHub events such as pull requests and deployment reviews, and propagates that context back to related Linear tickets