Suggestions
Mitchell Hashimoto
Software company with a freemium business model
Mitchell Hashimoto is a prominent figure in the tech industry, best known as the co-founder of HashiCorp, a company he established in 2012 alongside Armon Dadgar. HashiCorp specializes in tools for cloud infrastructure management, including popular products like Vagrant, Terraform, and Vault, which are widely used for automation and deployment in cloud environments.14
Early Life and Education
Hashimoto graduated from the University of Washington, where he met Dadgar while working on a research project. Their collaboration laid the groundwork for HashiCorp's founding.3
Career at HashiCorp
- Roles: Hashimoto served as CEO from 2012 to 2016 and later took on the role of co-CTO until stepping away from leadership positions in 2021. He transitioned to an individual contributor role before leaving the company entirely in December 2023.245
- Contributions: He played a crucial role in developing many of HashiCorp's key products, significantly impacting cloud infrastructure practices. Under his leadership, HashiCorp grew rapidly, reaching over 1,500 employees and numerous enterprise customers.45
Departure from HashiCorp
In December 2023, Hashimoto announced his departure from HashiCorp after more than 11 years with the company. His decision was influenced by personal reflections and a desire to spend more time with family. He expressed pride in what he had accomplished and emphasized the importance of building a self-sustaining company that could thrive without his day-to-day involvement.26
Personal Interests
Outside of his professional endeavors, Mitchell Hashimoto is also an FAA-licensed private pilot and enjoys flying various aircraft, including a Cirrus SF50 Vision Jet.5
Overall, Mitchell Hashimoto's legacy at HashiCorp is marked by innovation in cloud technology and a commitment to fostering a vibrant user community around open-source software.
Highlights
Another side effect of this: I can almost remove the "good first issue" (or "contributor friendly") tag. Every issue is contributor friendly in the sense they're all well scoped. I think I'll keep the tag around to highlight the easier issues, but its fun to think about.
I'm doing something new (for me) with Ghostty: the issue tracker is only for actionable tasks. Features in the issue tracker are accepted and well-scoped. Bugs are reproducible. PRs must have an associated issue (no drive-by PRs). The issue tracker is not used for discussion.
The one main benefit of this is maintainers and contributors can open up the issues tab and dive into anything. Every single issue is ready to be worked on. People who open a PR referencing an issue can have very high confidence their PR will be accepted.
In past OSS projects I've either started or been part of, the issue tracker has become a mess of Q&A, stale bug reports, and enhancement discussion. Drive-by PRs put burden on maintainers because they may implement an interesting feature but an undesirable way and saying no feels bad.
I also really hate issue bots. "Issue stale type /go-fuck-yourself to keep it open" is a system I've hated from both sides as a user and maintainer. (Bots that simply do categorization are good bots) The pattern I'm doing with Ghostty means issues in the issue tracker are never stale.
This time, all discussion is encouraged to use GH discussions. Once a bug is reproducible or a feature is designed in a way I approve of, it is converted to an issue. Some discussion happens in Discord/IRC too but I encourage it to eventually move to GH so it can be indexed by search engines.
We've been doing this for only about a month now and only within the context of a small (~2000 people) private beta, but so far I've thoroughly enjoyed the change in project management from it.
