Hack that pad …
I like the suggestion, since I guess you’re suggesting it, because worked at previous LOTEs, so go ahead! Why change a running system. Just some comments & questions:
-
Sounds good, will you post every single link to the wiki then in advance, too (or is it one link for all sessions, referring to #3?)? Will there be a little time in the very beginning of the event when everyone is gathered so that you could walk people through a short introduction into Hackpad? I expect lots of people to join the documentation team kinda spontaneously on the spot, so they might appreciate a short “how to”, if they never heard of Hackpad (the name alone can be a bit intimidating, as it slightly implies you gotta be techy). I’m thinking of the pen and paper crowd here and of how to best invite people in case this is a new form of doing things for them.
-
Good idea for people who like the communal documenting idea. I’d like to add that people should still be encouraged to find a good balance between trying this if they like, but not feel pushed if they prefer to do it in another way. For me, it would be very distracting to listen to the session while co-documenting with others. I would easily get lost in trying to read other people’s contributions - and have a lot of fun doing it - but get distracted. So yes, point to the Hackpad, and leave space for alternatives, so that people can do it the way they do it best.
Who would do this “pointing out”, then? Can the speakers be asked to refer to the Hackpad link / Documentation thread in the beginning? No one of us will be around at every session, so how can this work best for all?
Would it help to have a “how to document / Hackpad” poster in the room as a backup plan, so people can look up the basics there? Like this, for example:
-
Like co-documenting with others? Go to: https://lote5.hackpad.com/ and find the session. Group Hackpad on!
-
Like to document individually? Enjoy. After you’re done, please upload this here: “link in forum to be defined where the postings about sessions will be set up” and find the session you’d like to contribute your documentation to.
Or so …? Don’t know. How did you do it in the past so that it was clear where the documentation goes to? Before every session? Once at the very beginning of the event?
- Would that mean that it’s one large hackpack-document in the end? Would it then still be possible to link to individual parts of it, for example to add a link to the hackpad for session X to thread about session X?
More on general documentation/harvesting questions/coordination in next comment.
Cheers
Kaja
(but hope to do it as early as possible, preferably even before the afternoon.).
It would be very good to have a big wall for the things that will be written on post-its etc., so this now is about the pen and paper side of the game …
Looking forward to reading all about that session, which I probably won’t be able to join, myself.