Choice, Clarity, and the Future of Caching in Gradle Actions

News Blog + Comments
1

Since the release of gradle/actions v6, we’ve been listening closely to the feedback from the community. It’s clear that while we were focused on building the next generation of caching for Gradle, we missed the mark on how we communicated the changes to licensing that came with the release.

This is a companion discussion topic for the original entry at https://blog.gradle.org/choice-clarity-future-caching-gradle-actions
2 Likes
2

Chiming in again and thanking @daz for their hard work over the last several days to clarify this whole thing, listening to the community feedback and implementing changes to address concerns. Thank you so much for your efforts!

1 Like
4

You did, a number of other things wrong, and have destroyed trust. I got Auto upgraded by renovate before you even made the announcement that you had made The original change. It will be a long time before I trust Gradle again.

  1. You didn’t give the community a long heads up before releasing this.
  2. You made the change implicit opt in if you use the action at all.
  3. Unlike The Develocity plug-in decided not to make accepting the terms of service explicit. And now honestly I think I want that accepting to be done with a version so that I have time to review each license ahead of time.
  4. You’ve chosen to remain with an opaque binary. I suspect this is about money. You should look at source available licenses and perhaps roll your own if they’re not good enough.

Even in changing this now who’s to say you won’t behave the same in the future or even shadier by not announcing it at all.