We are excited also because we continue to have incredible support from the open-source community: not even 7 weeks old, our GitHub repo is trending since yesterday, we reached 3000 stars on our spec and we have more than 1200 forks.
Quite an exciting way to end 2022!
What’s coming next? We are expanding our opportunities to meet contributors at events, with quite a busy schedule in 2023 and also pushing further in our community effort to share the roadmap and vision with everyone who would like to participate in the Score journey.
Thank you for your continuous support, let’s chat more on Slack or on the discussion tab on GitHub!
The team behind Score
The idea for Score organically formed from looking at hundreds of delivery setups, across engineering orgs of all sizes (from startups to Fortune 100). We have all been involved in platform engineering and developer tooling for the past decade, in one way or another.Some of us built Internal Developer Platforms at the likes of Google, Apple or IBM, some come from the IaC side of things and played leading roles at companies like Hashicorp.
We all share the vision of developer and workload-centric development. We want to reduce cognitive load on developers and make sure engineers can spend their time coding and shipping features, instead of fighting config files.