Snapshot behind Fastly; roles and responsibilities
Hi all,
Snapshot is behind Fastly since Sunday Nov 17 2024. I think that's bad
and would like to change that. It's bad in the short term since we
expose user data to a third party. It's bad in the long term since the
short term bad won't go away until we learn how to deal with web
traffic.
I have not been able to solve the problem with more incoming HTTP
traffic than what the snapshot setup comfortably can deal with. Partly
because I'm not very knowledgeable in this field and partly because I
have not been given enough access to the cache layer(s).
DSA have legitimate concerns about exposing user data to people who do
not need access to it. Would it help if my relation to Debian was
formalised further than the current status of Debian Contributor?
More generally, I sometimes find it hard to understand the roles and
responsibilities wrt the snapshot service. This results in me on the one
hand being overly cautious with asking for some things and on the other
hand sometimes pestering the wrong people, most probably also in the
wrong way. It would be good to minimise unnecessary frustration and lost
calendar time.
There's a Snapshot service meeting today at 1700Z in #debian-snapshot
for all who are interested in helping out.
Reply to: