This was one of the biggest reasons that I was thinking screen casts instead of "video"; you want to show somebody how to use their device in a mainstream kind of way... and as much as we all love to admire each other, I think taking the "hey here's me using my tablet" out of the equation helps give these tutorials a much more polished and professional appearance (at the end of the day you want people to feel like what's being demonstrated will actually be easy and effective for them to do... people generally don't get that impression when they watch shady videos of tech savvy people "working the internet magic". No offense to Krisse of course (those videos were great!), but I honestly don't see everyone involved making their videos as clean and polished as the tablet school ones were, even if the guidelines are in place.)

When it's all said and done, I think the best approach would be a combination of written and video. The suggestion I have would be people do a detailed write up of how to do something (using table of content if you want/or a common format, whatever). That "rough tutorial" then gets submitted up to the forum/feedback place/proposal area, where somebody (community member, council person, somebody who dreams about Maemo at night, etc) can jump on, claim it as "their edit", and use the SDK and screen casting software to try it out as written. If it all works, then they save the video, add it to the tutorial and the whole shebang gets put up and online. If it doesn't work as expected or there's some confusion then the person doing the "trial run" emails/posts back to the original author that changes or clarification is required, and the process continues.

It's a good open check/balance setup that results in 1) everyone can contribute tuts, whether you know how to do video and screen casts or not 2) tuts are of higher quality because there's now a "quality control" type of process involved 3) tuts are written but always include the option of a video demo showing how things should work, without requiring any real extra effort (somebody completely new should always try your tut first anyways, so if they happen to be recording their efforts at the time...). Anyways again just my two cents, but that's very similiar to the editing process I've gone through when writing articles and chapters for web-related magazines and books, and it works very, very well.