Balkans/Events:2012/Zagreb/Aftermath/Feedback

Participant's thoughts

Gent Thaci

What was good

• Venue,
• Hotel,
• Food,
• Organizing.
• Community Balkans Members

What was bad

• Postponing sessions,
• Wake and meetup up in time to leave hotel.

Suggestions for improvement

• Agenda pre-set in time
• Etherpads prepared
• Different places to eat, more tradinional food.

Altin Ukshini

What was good

• Places (Hotel, Restaurants)
• Lunch, Dinner
• People (very friendly)

What was bad

• All things went up in hurry
• Agenda changed so often because speakers didnt prepare their presentations in time, and Etherpads should have been prepared earlier.

Suggestions for improvement

• Start preparing documents earlier for participants who have to apply for Visas.
• More places to visit...
• More hands on code/hacking/sessions

Novica Nakov

What was good

• big turnout
• meeting the local hacker community
• axel's and brian's patience

What was bad

• not enough hands-on stuff
• not enough power cords
• we should have spend more time on the swot.
• t-shirts with big football-like prints on the back :)

Suggestions for improvement

• more hands-on stuff

Oskar Ivanić

What was good

The Hotel, The Mozillians, The Food, The Logistics, and The Hack Lab visit

Dejan Binder

What was good

The hotel, the Mozillians, the positive atmosphere, the food, the visit to the hack lab, the logistics

What was bad

Not enough sights visited, the mix up around the agenda, the weather :D

Michelle Thorne

What was good

• Good turnout, good level of cooperation and interest
• Nice location, comfortable hotel
• Well-organized pick-up and drop-off for airport bus
• Yummy food
• Great to hear the country reports
• Friendly host team, very considerate and fun to work with.

What was bad

• More hands-on sessions would've helped create good energy, learn and discuss more intensely. Can be in small groups and allow people to participate in session that interest them.
• Important to give clear meeting times. Often confusion about when meeting vs. when things are starting.
• No plan for next steps. The SWOT analysis was helpful, but it would've been good to decide on next steps as a group.

Suggestions for improvement

• Mix up the groups. Not everything has to be in plenary with everyone. Sometimes smaller discussion/hacking groups are more effective.
• Structure the one day of sessions so that Sunday is for exploring, relaxing, hanging out together.
• Etherpads set up in advance for collaborative note-taking.

James Michael Dupont

What was good

• Food, Hotel, Travel, Rooms, people.

What was bad

• Planning was a bit chaotic.
• too much beer and energy drinks.

Suggestions for improvement

• get more sleep for the organizers
• we could have skipped friday, it would have been fine in two days. only sat was really used.