Carbon Aware SDK - Call for Features

[Sophietn]

Call for Features

The Carbon Aware SDK has just released v1.4!

We're now looking ahead, and planning out our future roadmap.
And we want to hear from those using the SDK.

What do YOU want next for the Carbon Aware SDK?

• Any features you'd love to see added?
• Any pain points you'd love to see fixed?

Leave your thoughts and ideas as comments below!
Once your idea is fully formed, Raise a Feature Contribution via our issue template.

This discussion is a Call for Features.
Whilst there's no guarantee your requests will be implemented, we want to gather feedback and hear directly from SDK users as to what you'd most like to see next.

[YaSuenag]

I'd like to propose Multiple data source. I believe this feature helps to operate onpremise and/or multi AZ system.

I proposed this feature in #345 , but it was closed as "stale" unfortunately. So I'm happy if we can raise this proposal again.

[bderusha]

I propose adding "Publishing the SDK as a NuGet package" be included on the roadmap.

There are a few things I would like to see happen as part of such work:

• Review + Merge the ADR-0006 implementation Implement Data Source Registration per ADR-0006 #366
• Update ADR-0014 to include a detailed proposal for how to split the project into packages
• Implementation of ADR-0014 to structure the code to support packaging
• Implementation of package publishing pipelines

Benefits:

• Creating a published "SDK package" opens up the SDK to a wider audience by making it easier to integrate into existing software, thereby increasing the impact of the project.
• Creating a "core package" allows community members to create their own DataSources without needing to clone the entire project.