[cross-project-issues-dev] yesterday's server outages

[Markus Knauer <mknauer@xxxxxxxxxxxxxxxxx>]

Hi all,

we've had a similar discussion lately about problems with Hudson servers and where to report such issues, which communication channels to use, etc. Yesterday we had a larger outage of the Eclipse infrastructure and there are still many things not working properly. 

Up to now I don't really know what happened (I've seen some random snippets of information on Twitter, here a bug from some committers, there a message on the mailing list from other committers), but what I do know is that a lot of us committers wasted time on tracking down problems in *their* projects, problems that were in fact related to infrastructure problems.

This morning I found out that there is a status page at https://dev.eclipse.org/committers/help/status.php available, but I think this is not enough. 

First, I think this kind of status should be available in a more prominent place where it can be found from people without deeper knowledge of Eclipse.org.

And then I'd like to have an improved communication in both directions:

We (the community, the committers) are currently using *all* communication channels to report such things, e.g. mailing lists, Bugzilla, Twitter, etc., to the webmasters. If they need to monitor all channels, they won't have time to spend on their work. We should look into this again if it can be improved.

In the other direction I may have missed something, but I was looking for mails in my inbox, blog posts, Planet Eclipse, etc but I wasn't able to find anything so far. I am totally fine with a message saying that there are known problems with LDAP, that it affects nearly every service and that you are investigating. A little 'hey, we are aware of it and we are looking into it' to the community would have been enough to calm down my heated mood.


Thanks,
Markus