Recently I’ve seen all kinds of communication with the sysadmin team that simply does not work. Here are some examples:

• Using random irc channels like #kde-devel for asking if systems are down. If you want to know that, use #kde-sysadmin.
• Assuming sysadmin knows of a problem. Sometime I only find out that a server is down after a few hours. Simply because everyone assumes someone else has reported it. Don’t ever assume it. Report a bug at https://bugs.kde.org/enter_sysadmin_request.cgi (it is in the footer of bugs.kde.org, so very simple to find
• A variation of that is silently assuming things. Say you tell us Foo and that we should deduct that Bar needs to be done and we undersand that. No we don’t. Be explicit, file a sysadmin bugreport.
• Trying to speed up things by filing a bug and approach us privately. No it won’t help, we usually process bugs very very quickly. Last week this caused double work, as Dirk was on irc and I was not and only saw the bugreport. So we did it twice. Really a waste of time.
• Sending a mail to sysadmin at kde dot org. This has a high chance to get lost and not processed at all. If you are lucky you get a mail back to report a bug in bugzilla. So why not use it in the first place?

I know communication is tough, but to keep it structured and managable, just file sysadmin bugreports. It is very simple (no wizard with multiple steps and duplication checks, just a one page web form) and it would help us a lot!