Hi Kristian, Thanks for your feedback, it's very important. I'm adding a few personal comments that I think are important and we [maybe] not mentioned.
2014-12-15 13:50 GMT+01:00 Kristian Rother <krot...@rubor.de>: > > > Dear Bilbao team, > > I read your proposal from one end to the other, understood all of it, and > I like what you already did for EuroPython. Here you find some comments to > your proposal. > > 1.) organizational skills > * Alexandre and some other team members obviously addicted to organizing > conferences. This is good. > * Lots of conference experience, also bigger ones. > * Professional company on board for catering etc. > > CONCLUSION: The team is experienced enough for something as big as > EuroPython. > > > 2.) Team > * Most of the team members are PhD's in CS. I was at little concrned that > the group might be exclusively academic, but the diversity of things you > have been doing speaks a different language. Excellent. > * I appreciate a lot that you got PyLadies on board early, and that this > is reflected in your team. Go on like this! > * You already assembled about 20 persons who declared they'd like to help. > Great! > > CONCLUSION: I think this team can do it! > > > 3.) Proposed Dates > * I like that you offer two possible dates. > * The timeline is in my opinion very, very tight. At the moment, I do not > see an active programme committee chair on the on the EPS, let alone a > committee. Unless there will happen a lot in the next few weeks, I see a > serious risk that the deadline cannot be met, therefore compromising > quality of the programme. > * For a conference in July, inviting keynote speakers should happen about > now. > * What about submission deadlines for trainings/workshops/sponsored talks? > > CONCLUSION: Risky. > I disagree on this. Mainly because the EPS has never had a programme committee chair, which was always something that was part of the local organizing team. From this year we are trying to start the permanent Workgroups (WGs) and the programme team is one of those. The previous EuroPython editions had different schedules and methodology from those adopted last year (or the ones used for Pycon US, i.e). Honestly I think that there are many options rather just one right option here. Still, I agree that with more time it's easier to mitigate random risks.. but we are doing our best. > > > 4.) Social Events > * I like the idea of something typical for the region. > * With a capacity of 200-600 this is a cool addition for those who don't > mind talking about Python on a bus for 3 hours. > * Cocktail party at the Guggenheim is very aproppriate. Great location! > * I had expected the Guggenheim option to appear in the first place before > the basque dinner, because it looks more like "the official conference > party". > * Gala dinner: OK as an option, but looks like "the usual" to me. > * Do you have any ideas for the programme during the event already? > * Guys, you have found lots of options. I think you should decide this on > your own! > > CONCLUSION: Yummy! > > > 5.) Venues > * You obviously did your homework. I am not an expert on the matter, but > both venues look big and professional enough. > * I would prefer Euskalduna because it is closer to the Sprint location. > Feedback on this is actually very important. There are actually also other aspects we are considering like: - prices - services available and included - location (not only regarding the sprints but also to city transportation, accomodation, touristic spots, etc..) - spaces for sponsors, catering, social breaks (coffee & lunch, outdor areas, etc..) If you have other opinions on that please tell us, it's really important. > > > 6.) Finance > * No idea. I assume you talked to both the local team for EP in Berlin and > Florence. > There is a budget proposal already. This is just *as is* and do not include some options (like financial aid, etc..). In general conference budget is something that will change until a few weeks after the conference. One really important thing to consider is that the budget and ticket prices proposal are nothing official and are very likely going to change. > > > 7.) Minor remarks > * There are red frames around links and footnotes when viewing PDF > (Ubuntu) > * 2.2 The first sentence should state what the company does. All other > sentences are optional. > > 8.) Communication > * Please provide an email address to the spokesperson of your team on the > first page. > * Please introduce yourself and the proposal on the EPS mailing list. You > can't expect Marc to do all the communication for you. BTW, I am curious to > get to know you and I guess I am not alone. > > I hope this information is helpful to you, and I wish you good luck with > organizing. > Thanks again for the feedback! All the best Fabio > > Best regards, > Kristian > > ---- > > Dr. Kristian Rother > krot...@academis.eu > +49 176 3052 4691 > www.academis.eu > > Create better science! > > _______________________________________________ > EuroPython-Improve mailing list > EuroPython-Improve@python.org > https://mail.python.org/mailman/listinfo/europython-improve > >
_______________________________________________ EuroPython-Improve mailing list EuroPython-Improve@python.org https://mail.python.org/mailman/listinfo/europython-improve
