-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Icebreaking #17
Comments
@bebatut I was hesitating to do a similar icebreaker this year. I thought last year's was OK, but was not a stunning success either. It was also a lot of work. That said, this year would be less work as the code already exists. I think using the questions from the registration would be a plus. However, many of those answers will be unique, making it difficult to find everyone on your list. (We would need to change the requirements for "winning".) And I would be strongly in favor of having name labels again. Without labels, people will just copy the names from other people's forms, or put people's names on without first talking to them (which is the whole point of this - talking to people) Finally, I like the idea of having lots of winners. |
I do it. |
@heylf: I'm working on a composite spreadsheet that unifies all registration information into one set of rows. However, I won't have it done until next week. Would that be useful to you? (I think it would, but it depends on your plans.) |
Definitely, makes the processing much easier. Thanks a lot! |
Game has been finished. Printing is on its way. |
Should we organize a icebreaking session?
Similar to the one last year (but using the "Ask me about" of the registration): everyone got a paper with several "find someone who..." and a white space for name, they need to fill it before Wednesday evening and we solve them on Thursday to give a small present (Bächlebot?) during the closing session.
What do you think?
@tnabtaf could you share what you used to prepare the icebreaker last year? Thanks a lot
The text was updated successfully, but these errors were encountered: