There's a long term plan to switch the wiki to being hosted on Emacs/Elnode. People could help out, especially with corner cases of the rendering. The repo is: https://github.com/aidalgol/elwiki
Note that we don't expect to do this quickly. Maybe we could get it up as a readonly mirror quite quickly.
Right now the issue is getting enough of the wiki cached that we're not under siege.
I'm clearly doing a bad UX job with this somehow. There are a collection of little videos wrapped by web pages documenting what is in the video. Eventually they will add up to something substantial (hopefully) and comprehensive (hopefully).
I toyed with the idea of using something that would show you the keys... but those things are never totally reliable and always a bit of added complexity. So I decided instead to offer the web page approach.
I admit, I'm probably not doing a great job for complete Emacs newbies right now. I am unclear if I have to, there are a lot of starting Emacs screencasts around. This one is about starting with EmacsLisp, not really Emacs.
Having said that... if that's what people want I may go back and alter the structure of the thing so that total newbies could join in.
It would probably only mean having fewer expectations in the crash course.
Yes. We're veterans of previous video startups. This is video meeting done right. It's not a big part of the product but it is important coz it means you don't need skype or hangout or whatever in addition to this.
If you ping me on twitter I'll make sure you're prioritized. We are obviously wanted teams to try this to tell us what is good and what isn't. So if you're a team we want you basically.
I'm not going to advertize it that much (because I don't want to support people that way yet) but all the code behind teamchat.net is freely available on github.
That's basically it. We've worked on this for quite a while and I reckon we could just keep going... This way we can gauge interest and prioritize teams who sign up.
And yes. I will publish results later in the week.
Note that we don't expect to do this quickly. Maybe we could get it up as a readonly mirror quite quickly.
Right now the issue is getting enough of the wiki cached that we're not under siege.