Skip to content
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

2015 Feedback #108

Open
iancrowther opened this issue Jan 1, 2016 · 1 comment
Open

2015 Feedback #108

iancrowther opened this issue Jan 1, 2016 · 1 comment

Comments

@iancrowther
Copy link
Member

We would to share the "lessons learnt" from 2015.

In order to help us, can you provide us wiht some feedback?

  • What went well?
  • What did you love?
  • What should we do again?
  • What could we do again?
  • What went wrong?
  • What could we imporve on?
  • What should we imporve on?
  • What was missing?

A quick comment will help us a lot. thanks!

@tdd
Copy link
Member

tdd commented Jan 2, 2016

Hey there,

OK I'll bite 😁 I organized the Paris edition of the 2015 NID.

What went well?

As usual, local org, catering, venue, etc. all went well.

What did you love?

The usual stuff we get at NS Paris: the energy, the vibes, the attendees' feedback, the serendipitous encounters…

What should we do again?
What could we do again?

A single day with as many events as possible certainly is nice.

What went wrong?

Last year it didn't really differ for us from any regular NS Paris (see further down). Not enough coordination AOT with other events in close TZ's, I'm afraid. We also failed to monitor our Twitter account for hollers from other chapters, and because of that let the ball drop on a couple nice invites to remotely participate on code/hardware interactions with them (my bad, sorry!).

Generally we didn't prepare for the international side of it, we just ran a regular session on the common date.

What could we improve on?
What should we improve on?
What was missing?

There really needs to be a well-defined set of channels (or even a single channel, e.g. Slack, Gitter or whatever) for people in near TZ's to communicate during the day. This is true for attendees and organizers both, but organizers in particular, in order to do last-minute syncing of stuff.

AOT discussions with TZ champions and chapter owners is certainly warranted in order to try and put together a few common happenings, be it through videoconferencing (Talky? Skype? Hangouts?…), remote API calls into public servers run at the session venues, PR code reviews of projects developed during the day in the open, or what have you.

Sharing pictures throughout the day in a common spot (e.g. Flickr pools per TZ or global, etc.) would be a great way to commune, too.

A good understanding of the other sessions in near TZ's (exact schedule, chapter owners contact info, intended tasks / format / size, etc.) would be good as well. Sizes and formats vary wildly from one chapter to the next, I gather.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants