Differences between revisions 3 and 11 (spanning 8 versions)
Revision 3 as of 2007-03-14 19:33:14
Size: 2687
Comment:
Revision 11 as of 2007-03-16 10:38:17
Size: 3992
Editor: 82-33-200-152
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
calendar. EuroPython 2007, the European Python and Zope Conference, calendar! EuroPython 2007, the European Python and Zope Conference,
Line 4: Line 4:
was a great success, featuring a variety of tracks, amazing lightning talks and
inspiring keynotes. But with your participation, we can make EuroPython 2007, the fifth EuroPython even more successful than the previous four.
was a great success, featuring a variety of tracks, amazing lightning talks and inspiring keynotes. But with your participation, we can make EuroPython 2007, the sixth EuroPython, even more successful than the previous four.
Line 7: Line 6:
This year, we have the following tracks planned: This year we have decided to borrow a few good ideas from PyCon. The first idea is to move away
from the 'track' structure. Instead, speakers are invited to submit presentations about anything
they have done with Python that they think would be of interest to the Python community. We
will then group them into related groups and schedule them in the space available. In the past,
Europython participants have found the following themes to be of interest:
Line 9: Line 12:
   Science/Refereed Papers
   Python Language and Libraries
   Web Frameworks
   Education (and everything else)
   Lightning Talks
   Open Space
 * Science
 * Python Language and Libraries
 * Web Related Techonologies
 * Education
* Games
 * Agile Methologies
and Testing
* Social Skills
Line 16: Line 20:
After the conference we will, as usual, be holding Sprints. There will also be a refereed paper track. The Call for Refereed Papers will be posted shortly.
Line 18: Line 22:
XXX click here for 'what is a sprint' and 'why should I sprint'?
XXX click here to propose a sprint
XXX for a list of sprints already proposed?
As usual we will be holding Lightning Talks. A Lightning Talk is a very short talk -- five
minutes maximum -- scheduled one after another. You can fit 10 of them in a 60 minute session.
There is no approval process: speakers merely sign up at the door. Topics are often up-and-coming
Python projects, cool hacks, things you wish were different, recruitment for a new Sprint
based on an idea you just had, war stories, and amusing mistakes. If a topic is boring, or
incomprehensible, don't worry, it will be over in five minutes!
Line 22: Line 29:
Open Space is a new concept for EuroPython. We've imported the idea from PyCon
and the Agile 2006 and XP 2006 conferences. An Open Space is an area reserved
for informal presentations, talks, demonstrations and discussions. Pretty much
anything is fair game. Important to the concept is that things are not planned
in advance. Instead, while at the conference, you reserve a time slot and
write down a title. If you are familiar with Lightning Talks, then you can think
of OpenSpace as non-plenary Lightning talks without the time limit.
The second idea we have borrowed from PyCon -- and from the Agile 2006 and XP 2006 conferences -- is
Open Space. Open Space provides a structured way to realise the main benefits of attending a conference: breaking down barriers between special interest groups and encouraging the sharing of experiences with other attendees. An Open Space is an area reserved for informal presentations,
talks, demonstrations and discussions. Like Lightning talks, Open Space is not planned in advance.
But unlike Lightning Talks, Open Space is not plenary, has a much more generous time limit. One
could use it to:
Line 30: Line 35:
This provides a structured way to realise the main benefits of attending a conference:
sharing experiences with the other attendees.
 * meet with like-minded folk to discuss a problem you all have.
Line 33: Line 37:
XXX sell this better - discussing/experience sharing is the main value not sure what
to add.
 * show off that cool program you have been writing.
Line 36: Line 39:
---  * have So-and-so give his talk again, for those of us who missed it the first time, or have him clarify the parts you found confusing with a demonstration.
Line 38: Line 41:
XXX There will be a refereed papers track as well this year, which will be
announced separately. -----how to rewrite this science/refereed being joined..
XXX lac: Ah, why are we merging this? Cannot write what I do not know.
XXX say that we are chosing to have fewer tracks this year. To this end
XXX Science and Refereed have been merged. And Education is now a big umbrella that
XXX convers 'Social Skills' and 'Methodologies' for those people who want to
XXX schedule a talk in those subjects. Or are we doing away with such things?
XXX hope not, lac
After the conference (from Thursday 12th July to Saturday 14th July) we will, as usual be holding Sprints: sessions of collaborative development focused on creating or improving software projects, documentation, and other materials. A sprint is a "two-or-three day focused development session,
in which a small group of developers pair off together in a room and focus on solving a particular problem or building a particular subsystem. This gets the team focused around clear (and challenging) goals while working collarobatively. Not only do is this a great way of getting results, but also a great way to get new people aquinted with the codebase, and disseminate knowledge withing the team.
Perhaps most important -- it's fun!
Line 47: Line 45:
To read a longer description of each track go here: To propose a sprint, or see what sprints are already proposed, visit http://www.python.org/moin/EuroPython2007Sprints .
Line 49: Line 47:
   http://indico.cern.ch/conferenceProgram.py?confId=44

XXX fix track descriptions, update and fix link

To submit a talk, go here:

   http://indico.cern.ch/abstractSubmission.py?confId=44
To propose a presentation, go to http://indico.cern.ch/abstractSubmission.py?confId=13919
Line 61: Line 53:
XXX make sure all necessary info is updated Looking forward to seeing what you fine folk have been up to,
the EuroPython Team
Line 63: Line 56:
XXX also mention sprint dates and where to propose sprints
(12-14th of July).
Discussion:

I used the word presentation rather than talk, because some people's talks are more like demos. As long as we don't get 'This is my company. Here is my product. Buy me.' I am fine with this. If others are not, change presentation back to talk.

Book Monday 9th of July to Wednesday 11th of July 2007 in your calendar! EuroPython 2007, the European Python and Zope Conference, will be held in Vilnius, Lithuania. Last year's conference was a great success, featuring a variety of tracks, amazing lightning talks and inspiring keynotes. But with your participation, we can make EuroPython 2007, the sixth EuroPython, even more successful than the previous four.

This year we have decided to borrow a few good ideas from PyCon. The first idea is to move away from the 'track' structure. Instead, speakers are invited to submit presentations about anything they have done with Python that they think would be of interest to the Python community. We will then group them into related groups and schedule them in the space available. In the past, Europython participants have found the following themes to be of interest:

  • Science
  • Python Language and Libraries
  • Web Related Techonologies
  • Education
  • Games
  • Agile Methologies and Testing
  • Social Skills

There will also be a refereed paper track. The Call for Refereed Papers will be posted shortly.

As usual we will be holding Lightning Talks. A Lightning Talk is a very short talk -- five minutes maximum -- scheduled one after another. You can fit 10 of them in a 60 minute session. There is no approval process: speakers merely sign up at the door. Topics are often up-and-coming Python projects, cool hacks, things you wish were different, recruitment for a new Sprint based on an idea you just had, war stories, and amusing mistakes. If a topic is boring, or incomprehensible, don't worry, it will be over in five minutes!

The second idea we have borrowed from PyCon -- and from the Agile 2006 and XP 2006 conferences -- is Open Space. Open Space provides a structured way to realise the main benefits of attending a conference: breaking down barriers between special interest groups and encouraging the sharing of experiences with other attendees. An Open Space is an area reserved for informal presentations, talks, demonstrations and discussions. Like Lightning talks, Open Space is not planned in advance. But unlike Lightning Talks, Open Space is not plenary, has a much more generous time limit. One could use it to:

  • meet with like-minded folk to discuss a problem you all have.
  • show off that cool program you have been writing.
  • have So-and-so give his talk again, for those of us who missed it the first time, or have him clarify the parts you found confusing with a demonstration.

After the conference (from Thursday 12th July to Saturday 14th July) we will, as usual be holding Sprints: sessions of collaborative development focused on creating or improving software projects, documentation, and other materials. A sprint is a "two-or-three day focused development session, in which a small group of developers pair off together in a room and focus on solving a particular problem or building a particular subsystem. This gets the team focused around clear (and challenging) goals while working collarobatively. Not only do is this a great way of getting results, but also a great way to get new people aquinted with the codebase, and disseminate knowledge withing the team. Perhaps most important -- it's fun!

To propose a sprint, or see what sprints are already proposed, visit http://www.python.org/moin/EuroPython2007Sprints .

To propose a presentation, go to http://indico.cern.ch/abstractSubmission.py?confId=13919

For more general information on the conference, please visit:

Looking forward to seeing what you fine folk have been up to, the EuroPython Team

Discussion:

I used the word presentation rather than talk, because some people's talks are more like demos. As long as we don't get 'This is my company. Here is my product. Buy me.' I am fine with this. If others are not, change presentation back to talk.

EuroPython/2007/CallForProposals (last edited 2008-11-15 13:59:40 by localhost)

Unable to edit the page? See the FrontPage for instructions.