Differences between revisions 13 and 15 (spanning 2 versions)
Revision 13 as of 2007-03-16 10:49:32
Size: 3991
Editor: ArminRigo
Comment:
Revision 15 as of 2007-03-16 11:59:43
Size: 4515
Editor: PaulBoddie
Comment: Style changes (capitalisation), some rewording, spelling, headings.
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= EuroPython 2007: Call for Proposals =
Line 6: Line 8:
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:
== Talks, Papers and Themes ==

T
his 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 arrange 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 20: Line 21:
There will also be a refereed paper track. The Call for Refereed Papers will be posted shortly. In addition to talks, we will also accept full paper submissions about any of the above themes. The Call for Refereed Papers will be posted shortly.
Line 22: Line 23:
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
== Lightning Talks ==

As usual we will be holding ''lightning talks''. A lightning talk is a very short talk - five minutes maximum - scheduled in rapid succession, with as many as 10 lightning talks 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, less well-known 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
Line 29: Line 28:
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:
== Open Spaces ==
Line 35: Line 30:
 * meet with like-minded folk to discuss a problem you all have. The second idea we have borrowed from PyCon (and from the Agile 2006 and XP 2006 conferences) is the concept of the
''open space''. Open spaces provide 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 spaces are not planned in advance.
But unlike lightning talks, open spaces are not plenary, have a much more generous time limit. One could use it to...
Line 37: Line 34:
 * meet with like-minded folk to discuss a problem you all have.
Line 38: Line 36:
 * have someone give their talk again, for those of us who missed it the first time, or have them clarify the parts you found confusing with a demonstration.
Line 39: Line 38:
 * 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. == Sprints ==
Line 41: Line 40:
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!
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 focused two- or three-day 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 collaboratively. 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 within the team. Perhaps most important: it's fun!
Line 45: Line 42:
To propose a sprint, or see what sprints are already proposed, visit http://www.python.org/moin/EuroPython2007Sprints . == Your Contribution ==
Line 47: Line 44:
To propose a presentation, go to http://indico.cern.ch/abstractSubmission.py?confId=13919 To propose a sprint, or see what sprints are already proposed, visit...
Line 49: Line 46:
For more general information on the conference, please visit:    http://www.python.org/moin/EuroPython2007Sprints

To propose a talk or a paper, go to...

   http://indico.cern.ch/abstractSubmission.py?confId=13919

For more general information on the conference, please visit...
Line 54: Line 57:
the EuroPython Team 
T
he EuroPython Team

----
Line 59: Line 65:

Presentation, talk, seminar - perhaps only the last one is less likely to be interpreted commercially, but it's not really appropriate here. I've tried to make the terminology mostly consistent, however. -- PaulBoddie

EuroPython 2007: Call for Proposals

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 five.

Talks, Papers and Themes

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 arrange 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 Technologies
  • Education
  • Games
  • Agile Methologies and Testing
  • Social Skills

In addition to talks, we will also accept full paper submissions about any of the above themes. The Call for Refereed Papers will be posted shortly.

Lightning Talks

As usual we will be holding lightning talks. A lightning talk is a very short talk - five minutes maximum - scheduled in rapid succession, with as many as 10 lightning talks 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, less well-known 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!

Open Spaces

The second idea we have borrowed from PyCon (and from the Agile 2006 and XP 2006 conferences) is the concept of the open space. Open spaces provide 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 spaces are not planned in advance. But unlike lightning talks, open spaces are not plenary, have 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 someone give their talk again, for those of us who missed it the first time, or have them clarify the parts you found confusing with a demonstration.

Sprints

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 focused two- or three-day 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 collaboratively. 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 within the team. Perhaps most important: it's fun!

Your Contribution

To propose a sprint, or see what sprints are already proposed, visit...

To propose a talk or a paper, go to...

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.

Presentation, talk, seminar - perhaps only the last one is less likely to be interpreted commercially, but it's not really appropriate here. I've tried to make the terminology mostly consistent, however. -- PaulBoddie

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

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