<br><div class="gmail_quote"><a href="http://wiki.python.org/moin/PythonEvents" target="_blank">http://wiki.python.org/moin/PythonEvents</a> looks useful, but underused, and insufficiently well-known.<br><br>... but, of course, event organizers may not think to get an event listed there until long after they've made their decision, and you've made yours. It definitely doesn't meet your yearlong planning horizon requirement... I wonder if there's any hope of getting that level of planning. Our first PyOhio took place about four months after we first *imagined* it...<br>
<div class="im"><br><br><div class="gmail_quote">On Tue, Apr 20, 2010 at 12:01 PM, Mike Müller <span dir="ltr"><<a href="mailto:mmueller@python-academy.de" target="_blank">mmueller@python-academy.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I would like to have a kind of long-term internal planning<br>
calendar for Python event organizers. Something like a wiki<br>
page with login for list members for instance.<br>
Planning horizon should be one year and more.<br></blockquote></div>-- <br></div></div>- Catherine<br><a href="http://catherinedevlin.blogspot.com/">http://catherinedevlin.blogspot.com/</a><br>*** PyOhio 2010 * July 31 - Aug 1 * Columbus, OH * <a href="http://pyohio.org">pyohio.org</a> ***<br>