First accessibility scrum call is a failure

Dharmesh and I were the only two folks to attend the scrum call. This is probably because we're in the same office and I went and pulled him into the meeting. So, the question is, how did the tools fail?

Dharmesh and I went through the Google Event creation/invitation process and it's not good. You only get notification of an invitation to an event in your notification stream, not your email. And nobody checks their Google notification stream; it's just too cluttered and non-obvious.

Second, I can't attach a hangout to an event (WTF?). The Hangout needs to be created on-demand before the meeting and each individual must be invited. I really want the meeting to include video and voice, so I will try this again and see if I'm just doing it wrong.

Thirdly, no one was on IRC or twitter. I invited individuals directly who responded to the event invite, but no one answered the call and joined the hangout. No one out of 9 individuals. If we want to fix accessibility in Drupal, then we need to get involved with development and testing, not just talk about what we do. I want this scrum call to be focused on the nuts and bolts of what we're each interested in and what we're doing to bring that interest into code.

So I implore folks to make this scrum a reality. A little social pressure and visibility goes a long way to motivating us to build the tools we know we need.

If this was a tool failure, then we'll fix the tools. I don't care what tools we use, as long as everyone can use them and they give us the sense of connection that adds some humanity to an otherwise asynchronous and distributed effort.

Please leave comments if you tried to join but couldn't or didn't know how or weren't invited (sorry!) and we'll make it work.