Unfortunately we weren’t able to make much progress since the last update. We were in touch with Tigris, who were keen to make sure we have everything we need. Sadly @edef capacity to do work is severely reduced due to ongoing health issues, and my ability to support her is limited to being there to talk.
Since, thanks to @ron’s effort, Amazon significantly raised our allowance, the pressure is off for the time being. The foundation currently has no storage costs, to my knowledge. But the ultimate goal is still to substantially reduce the resource consumption, as we can’t rely on sponsorship forever, which in principle may and at any time.
Right now there’s no one really “owning” the cache in the sense of being capable, available, responsible, and accountable to make and implement decisions, including big changes. The arrangement set up end of last year with @flokli and @edef was supposed to change that, but it didn’t work out for multiple reasons. I had picked this up mid-2024 to see if we can keep things on track, so I still keep an eye on it – but I can’t do the actual work, this is not my area of expertise and I have other commitments that prevent me from leaning into it.
@zimbatm recently gave @Mic92 the necessary permissions to be able to do (small?) things in the meantime as needed. That is only a solution for maintenance mode and therefore mereley a temporary measure. This is why I’m supporting @Erethon to onboard into the infra team, who has the relevant experience, already helped us a great deal with devops for Summer of Nix, and has proven to be a reliable collaborator. He’ll assist us to get the work-in-progress security tracker deployed, which could be a stepping stone to get the cache migration moving again. I’ll take care of managing the foundation’s financial capacity to make this economically viable and sustainable, in consultation with @ron until the steering committee becomes operational.