|
Size: 3203
Comment: Tidied up, concentrating discussion, added links.
|
Size: 4060
Comment: cfp rewritten to take in the themes idea
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 6: | 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 do away with 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 8: | Line 12: |
| * Science/Refereed Papers | * Science |
| Line 11: | Line 15: |
| * Education (and everything else) * Lightning Talks * Open Space |
* Education * Games * Agile Methologies and Testing * Social Skills |
| Line 15: | Line 20: |
| After the conference (from Thursday 12th July to Saturday 14th July) we will, as in previous years, be holding sprints: sessions of collaborative development focused on creating or improving software projects, documentation, and other materials. | There will also be a refereed paper track. The Call for Refereed Papers will be posted shortly. |
| Line 17: | Line 22: |
| * XXX click here for 'what is a sprint' and 'why should I sprint'? * [http://www.python.org/moin/EuroPython2007Sprints 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 21: | 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. An important part of 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 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 23: | Line 35: |
| This provides a structured way to realise the main benefits of attending a conference: to break down barriers between special interest groups and encourage the sharing of experiences with other attendees. | * meet with like-minded folk to discuss a problem you all have. |
| Line 25: | Line 37: |
| ---- | * show off that cool program you have been writing. |
| Line 27: | Line 39: |
| (Discussion) | * 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 29: | Line 41: |
| XXX sell this better - discussing/experience sharing is the main value not sure what to add. | 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 31: | Line 45: |
| 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.. | To propose a sprint, or see what sprints are already proposed, visit http://www.python.org/moin/EuroPython2007Sprints . |
| Line 33: | Line 47: |
| ---- This year, talks with a scientific theme will be presented alongside refereed papers. This merge reflects the common themes of both tracks in previous years, and it provides a focus for contributors with backgrounds in peer-reviewed fields of work and study. --- DB ---- (Discussion) XXX lac: Ah, why are we merging this? Cannot write what I do not know. say that we are chosing to have fewer tracks this year. To this end Science and Refereed have been merged. And Education is now a big umbrella that convers 'Social Skills' and 'Methodologies' for those people who want to schedule a talk in those subjects. Or are we doing away with such things? hope not, lac ---- To read a longer description of each track go here: 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, XXX fill in what we want people to do. Is http://indico.cern.ch/abstractSubmission.py?confId=44 correct? Also, 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. |
| Line 59: | Line 57: |
| XXX make sure all necessary info is updated | XXX do we sign this thing? If so, how about: Looking forward to seeing what you fine folk have been up to, the EuroPython Team |
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 fifth 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 do away with 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 Frameworks
- 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 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, XXX fill in what we want people to do. Is http://indico.cern.ch/abstractSubmission.py?confId=44 correct? Also, 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.
For more general information on the conference, please visit:
XXX do we sign this thing? If so, how about:
Looking forward to seeing what you fine folk have been up to, the EuroPython Team