What’s next for Score in 2023

2022 was a big year for Score. Let’s highlight the community’s biggest accomplishments so far and look ahead to what is coming next.

2022 was a short but eventful year for Score. After its launch in early November, the score spec repository reached 1k GitHub stars in December and 5k stars in January. What a ride! We’re overwhelmed by this response and grateful for all the contributions and feedback we received along the way. 

The team behind Score took some time to reflect on the last couple of months and discuss focus items for Score in 2023.

2022 Review & Highlights

Let's set the scene: In the months before launching Score, we spend a lot of time discussing the philosophy behind Score as well as various solution approaches. We started with a handful of problem statements surrounding issues such as configuration drift, local configuration mismanagement, cognitive overload, knowledge silos and more. From these, we formulated an approach – workload-centric development – and started deriving a solution – platform-agnostic workload specification file – from there.

In November 2022, the Score Specification was launched alongside two example reference implementations (score-compose and score-helm). The project was still early, no question, but we were eager to get the word out and share our vision for Score with the developer community. Our focus for the first couple of weeks was to engage in discussions, validate problem and solution statements and gather user feedback.

Looking back on the year, our personal highlights of 2022 were:

Community events

We discussed Score and our vision for workload-centric development in front of a variety of audiences. It’s been a great experience to connect with the open source community and exchange ideas. We’re grateful for everyone who took the time to get involved.

If you’re interested in joining our upcoming events, keep an eye out on our blog and community Slack for updates.

Community discussions

The future of Score depends on community input. We were excited to engage in first round of interesting (and challenging) discussions, such as:

You’ll find further discussion threads in our community Slack. We’re looking forward to keeping the conversation going in 2023.

Feature requests

Score is still new. The community provided a lot of great feedback on how we can improve the maturity of the tool. These feature requests were the most popular:

You can find an overview of all issues here. If you’d like to get involved check our contribution guidelines.

2022 left us excited for 2023. It’s been great to see that the idea and vision behind Score resonates with developers, which brings us to 2023…

2023 and beyond

Our long term vision for Score is to grow a community for discussing topics like cloud native development, developer tooling and developer experience. We hope to create a space where developers come together to share experiences and explore new ways of working. The goal for the tool itself is to implement:

Curious to explore one of these topics in more detail but aren’t sure where or how to start? Reach out to share your ideas and we’ll do our best to provide additional product input to get you started and support you along the way. 

All contributions are welcome. Playing around with the tool and providing feedback, engaging in discussions or simply sharing your questions with us is a huge help. If you’re interested in testing or adopting Score with your team we’re open to supporting you with the onboarding and integration of the tool.

We’re excited to move things forward together with you and the rest of the community in 2023. It’ll be great to see where we’ll stand at the end of this quarter and year. If there’s something you’d like to discuss, drop in during our weekly office hours on Slack every Monday between 4 and 5pm CET. See you there!

Happy 2023!

The Score Team

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.

Configure once. Deploy anywhere. From local to prod.