[AndrewUnmuted]

My first reaction was very different from yours; the desire to dogfood feels excessive, to me, and negates the point in having a public roadmap in the first place.

Am I wrong for presuming that the people who would most care about GitHub's public roadmap probably aren't even GitHub users?

EDIT: Thanks for the replies, everyone. Seems like I hadn't fully comprehended the range of features available to paying members - given this knowledge, choosing to do the roadmap in this form makes more sense to me.

[iaresee]

Am I wrong for presuming that the people who would most care about GitHub's public roadmap probably aren't even GitHub users?

Free tier users, maybe not.

But paying users care very much about what they can expect for their outlay of money in the years to come. Roadmap presentations for paid software are _de rigueur_; they help keep your paying customers on your platform.. They're just not often shared openly like this.

Github has a vested interest in attracting more and more free-tier customers though. Then they go to companies and influence tool purchasing decisions and help feed the paying customer funnel. So this seems like a risk with some postive calculus behind it. It could be that free-tier users didn't know they wanted to know the roadmap, and now that they do they'll be happy they know about it.

[codeviking]

> Am I wrong for presuming that the people who would most care about GitHub's public roadmap probably aren't even GitHub users?

I think so. I'm a GitHub user and I like being able to view their roadmap.

Think about it this way. GitHub is a giant piece of software that developers use. Software changes, and developers are particularly sensitive to this. We're constantly fixing bugs and factoring code to support dependency shifts (or choosing to snapshot ourselves at some preestablished point of stability).

Given our sensitivity to change and how important GitHub's product is to our productivity it's crucial that we're not hit with surprises. A properly communicated roadmap helps avoid that -- thought admittedly it does take some work on our part as customers to parse it. That said this is no different than reading release notes and documentation for the software and libraries we use elsewhere in our day to day.

[shankun]

(From GitHub product team)

Thank you! We couldn't have said it better ourselves. Let us know if you have any other feedback on what we can provide you to plan better. And thanks for your use of GitHub!