Hello everyone,
The GNOME Infrastructure Team has spent the last few weeks focusing on optimizing our AWS data transfer costs.
I want to take a moment to clarify how we utilize these resources. The GNOME Foundation does not pay out-of-pocket for its AWS consumption; instead, we are fortunate to receive credits through the AWS Open Source Program. While this supports our operations, we remain committed to being responsible stewards of these resources by keeping our consumption within sustainable boundaries. We hope this provides clear context and avoids any unnecessary speculation regarding the Foundation’s financials.
I am happy to announce that the measures we’ve recently adopted to contain credit usage are already showing positive results. A key part of this success involves a new approach to Git pull caching.
By leveraging our partnership with Fastly, we are now using their CDN network to serve Git content closer to the edge. This change has two major benefits:
-
Improved Performance: Faster pull speeds for developers globally.
-
Sovereignty: We have officially dropped the HTTPS Git pull redirect to our GitHub mirror, serving traffic directly from our own infrastructure again.
If you’re interested in the technical architecture behind this move, I’ve documented the details in a blog post: GNOME GitLab Git traffic caching - Andrea Veri's Blog.
Thanks,
Andrea