Please join the team as reviewer or as volunteer. Please be constructive in order to help organizing the 2014 conference…otherwise please keep your energy for the 2015 organization. The 2014 organization does not happen _here_.
Regards, Andreas Am 13.02.2014 um 16:22 schrieb Rob Collins <rob.coll...@pythonpro.co.uk>: > Let's keep the affordable "community" origins of EuroPython. > *** Simple is better than complex. *** > > Some people are asking for clarity and openness. > *** Explicit is better than implicit. *** > *** If the implementation is hard to explain, it's a bad idea. *** > > Some people are raising exceptions for discussion. > *** Errors should never pass silently. *** > > The alternative to EAFP is LBYL, not "Tough. This is how it is. Keep quiet." > > So let's take a specific example: in the Verband conference proposal, under > "Expected differences from EuroPython 2010/2011/2012" they listed only two > items: Scholar students, and Barcamp. No mention of abandoning the binding > requirement to use the Python Italia website platform. No mention of > replacing community voting with a closed talk selection process. > > I like the idea of everyone getting a say on all the talks proposed. Let's > apply the Zen of Python, and discuss why we can't still have community voting > for EuroPython 2014. > > Rob Collins > _______________________________________________ > EuroPython 2014 – Berlin, 21th–27th July > EuroPython mailing list > EuroPython@python.org > https://mail.python.org/mailman/listinfo/europython _______________________________________________ EuroPython 2014 Berlin, 21th27th July EuroPython mailing list EuroPython@python.org https://mail.python.org/mailman/listinfo/europython
