|
Size: 2783
Comment: Trying to generate some kind of buzz ...
|
Size: 1292
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| Topics for PyCon DC 2003. | |
| Line 4: | Line 3: |
| PyCon DC 2003 is not going to be an elitist conference. It needs your help to ensure that there is something for everybody? What can you do? Well, firstly you can contribute your ideas on this very page. It's easy to edit Wiki content, so get to it! The more contributors we have, the mroe relevant and interesting PyCon DC 2003 will become. A few topics are listed below to get you started, but you should feel free to add more if you believe the PythonCommunities will benefit from having them covered at this, and future, conferences. | = Chairman's Plea for Help = |
| Line 6: | Line 5: |
| === Sprints === | Help. Is there a PyConWikiGnome in the house? |
| Line 8: | Line 7: |
| The sprints are intended to benefit the Python core, as well as encouraging more developers to take part in Python's development. They might also be a good place to see ExtremeProgramming or other AgileDevelopment techniques in action. What would you like to see done, or at least attempted? | ["PyConDC2005"] is now coming, and only Skip Montanaro is listening (hi, Skip). Good news: Jim Fulton has agreed to run the Open Space "track" and manage the sprints this year. |
| Line 10: | Line 9: |
| === Lighteniing Talks === | See the SteveHolden page for the chairman's current thoughts on organization and content. |
| Line 12: | Line 11: |
| At IPC 10 the Developer Day has many short talks on diverse topics. If you can't produce a full-blown paper, either offer your own talk (as short as five minutes is acceptable) to distil a part of your hard-won experience and save others the learning time you put in. Or just say what you'd like someone else to give a lightening talk on. | = Previous conferences: = |
| Line 14: | Line 13: |
| === Volunteers === | * ["PyConDC2004"] * ["PyConDC2003"] |
| Line 16: | Line 16: |
| The absence of professional organizers is the main way to keep the cost of PyCon down, but this means we're relying on YOU to help. Volunteer efforts don't need to be all-embracing -- if we can share the load then no one individual needs to suffer a heart attack to make things happen. This section will detail areas where help is needed, and you are encouraged to put your name down to offer assistance. Make it ''your'' conference. Make it ''our'' conference. This is a commmunity effort, and it needs people to ''''get involved''''. | = Notes from the gnome: = |
| Line 18: | Line 18: |
| === Progress Reports === | I've moved the pages linked from ["PyConDC2004"] and ["PyConDC2003"] (at least, those that are specific to them) to subpages. Doing the same for any pages created for ["PyConDC2005"] would save some cleaning next year. -- JohannesGijsbers |
| Line 20: | Line 20: |
| There are many areas of Python development where it's hard to stay in touch with what's going on. What would you like to see reports about? Two areas that have already been mentioned are Jython/JPython and the PythonBusinessForum. What else is of burning interest? Who is going to give these reports. Sign up here and help to make PyCon ''relevant'' and ''engaging''. You don't need to be a professional speaker to help other Pythonistas out with a little informatioppn. | ''Many thanks for the gnoming! I presume you mean that rather than having "PyConSpeakers" we should have "PyCon2005Speakers" directly? That's a good idea. What should we then use the "Pure PyCon" (with no year in their names) pages for? - SH'' |
| Line 22: | Line 22: |
| === Batteries to be Included === There seems to be some interest in building Python distributions that combine the core with various third-party libraries. ActiveState is probably the model here, packaging the Python core with Mark Hammond's win32all extensions and various others. How can this bve dome in ways that make more people's lives easier and at the same time assist the conference theme of "''''Popularizing Python''''"? |
Information that will still be relevant for the next year. That would mean there would be no "PyConSpeakers" page, but the PyConHelpers page could be useful over multiple years. Oh, and I think using subpages ("PyConDC2005/Speakers") would be better than "PyCon2005Speakers". -- JohannesGijsbers ---- CategoryPyCon |
Chairman's Plea for Help
Help. Is there a PyConWikiGnome in the house?
["PyConDC2005"] is now coming, and only Skip Montanaro is listening (hi, Skip). Good news: Jim Fulton has agreed to run the Open Space "track" and manage the sprints this year.
See the SteveHolden page for the chairman's current thoughts on organization and content.
Previous conferences:
- ["PyConDC2004"]
- ["PyConDC2003"]
Notes from the gnome:
I've moved the pages linked from ["PyConDC2004"] and ["PyConDC2003"] (at least, those that are specific to them) to subpages. Doing the same for any pages created for ["PyConDC2005"] would save some cleaning next year. -- JohannesGijsbers
Many thanks for the gnoming! I presume you mean that rather than having "PyConSpeakers" we should have "PyCon2005Speakers" directly? That's a good idea. What should we then use the "Pure PyCon" (with no year in their names) pages for? - SH
Information that will still be relevant for the next year. That would mean there would be no "PyConSpeakers" page, but the PyConHelpers page could be useful over multiple years. Oh, and I think using subpages ("PyConDC2005/Speakers") would be better than "PyCon2005Speakers". -- JohannesGijsbers