Eli Zaretskii wrote: > Corwin Brust wrote: > > There was an outage affecting all FSF hosted infrastructure for about > > the last twelve hours, ending around an hour back. Things should be > > stable or stabilizing now. (There is still some checking and > > restarting of things on the Savannah side as of this minute.) > > Sadly, these outages happen lately almost every day. It make our work > as GNU maintainers harder than it has to be.
I feel the pain. It's certainly been a problem. It's an issue we discuss in meetings with FSF sysadmin rather routinely. > I really hope this will get better soon. All I can say is that it is an active problem that we are actively working on improving. I can't say that we are all in agreement about the right things to do to improve it. We disagree on things. But it's a civil disagreement and we keep working together and we continue to have continuous improvement. > > This is the spot to check for announcements when FSF sysops cannot use > > it's own email and other services to let us know what's up: > > > > https://hostux.social/@fsfstatus > > Sadly, when these problems happen, there's usually nothing pertinent > on that site. The information about connectivity problems appears > there hours after the problems start. Fair point. More than fair. Look for changes in the announcement detail from today forward. FSF sysadmin has allowed access to post status updates starting today forward to the somewhat larger SysOps team. This means Savannah system status updates can now start to be posted there now moving forward. This was not previously available to us. That's a positive direction change for communicating what's happening. Bob
