IF Project updates 2024-12-12

[Joseph Cook]

Hi everyone,

It's my pleasure to report that we've raised a motion with the GSF Steering Committee to graduate the Impact Framework project! This is a huge milestone for the project and the graduation will coincide with our v1.0 release.

Preparing to raise the motion has dominated the past fortnight. We have been focused on cleaning up the repository, filling in any gaps in our test coverage, making sure our documentation is up to date, auditing our compliance with security best practices and gathering testimonials.

Our v1.0-beta release is available now for testing, and we'll upgrade it to a full release when the graduation is ratified. 

Post-graduation, we won't have a full-time development team working on IF anymore. Continued development will be reactive to feature requests and bug reports coming from our users. There will still be a small core team maintaining the repositories, docs and managing the mailing lists and discussion boards, but our focus will be more on driving adoption and integrations rather than proactively developing features.

Thanks to everyone who has helped get us to this big milestone!

The motion is open for discussion until 24th December, here.

https://github.com/Green-Software-Foundation/governance/issues/1

Cheers

Joseph

 

--

*****************

Joseph Cook

R&D Lead

Product Owner: Impact Framework, 

Green Software Foundation

*****************

[Joseph Cook]

Hi Thomas,

Thanks!

To be clear, the graduation is for the Impact Framework itself, which includes our "standard library" of plugins that come bundled with IF - we refer to these as "builtins". However, the community plugins are separate - they are developed by open source contributors and sit in external repositories owned by the contributors - they are not part of IF itself. 

Adoption will necessarily include expanding the set of IF plugins to some extent. What we've observed so far is that plugins are very useful for connecting IF with third party applications, especially if they expose an API (examples include the EcoCI Github plugin, WattTime, Azure importer, etc) or for implementing custom logic that is too complex to be concisely represented as a sequence of simple arithmetic or io operations served by our builtins (e.g. our CO2js reimplementation), but I've been surprised by how much people have managed to do just using our standard library!

I do expect the developer relations committee to be helpful in driving adoption. I know devrels influence the tools that get adopted by developer communities, so I'll be very keen to train folks from the devrel community to use IF and help them to evangelize however I can. A lot of the people we are talking to now are coming to us either because one of our members has spread the word or they've seen Asim and I talk and/or write - I do think the devrels can boost this in the new year.

Cheers

Joseph

On Thu, 12 Dec 2024 at 22:42, Thomas Lewis <thol...@microsoft.com> wrote:

Congratulations on this accomplishment! This is great news!

Will the adoption also include building of plug-ins? Will the upcoming Developer Relations committee be supporting or helping drive adoption?

 

 

Thomas Lewis

Microsoft Developer Relations | Spatial Computing & Green Software Engineering Developer Advocate

Twitter: tommylee | LinkedIn: aka.ms/thomas-lewis-linkedin

 

Book time to meet with me

---

From: Joseph Cook <jos...@greensoftware.foundation>
Sent: Thursday, December 12, 2024 2:32 AM
To: [public] if-community <if-com...@greensoftware.foundation>; [proj] impact engine framework <carb...@greensoftware.foundation>
Subject: [EXTERNAL] IF Project updates 2024-12-12

 

--
You received this message because you are subscribed to the Google Groups "[proj] impact engine framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to carbon-ql+...@greensoftware.foundation.
To view this discussion, visit https://groups.google.com/a/greensoftware.foundation/d/msgid/carbon-ql/CAPM5cucKrLRVXZtadcCyN%2B2p%2B_KE9YuzRer-R2L%2ByEmLSv2Zdw%40mail.gmail.com.