Thanks for a thoughtful response, Selena. Since I started this thread by griping, I should probably start by thanking you for your hard work. Thank you.<div><br></div><div>I would have commented on your session list earlier, but I was unaware that you had made final selections until this morning, when it occurred to me that I should check if I was on the hook for the Django session that I submitted. My bad, probably.</div>
<div><br></div><div>Your offer to nominate an additional Python session is a generous one. I hope this touches off a discussion here about what we might suggest.</div><div><br></div><div>Dylan</div><div><br></div><div><br>
<br><div class="gmail_quote">On Thu, May 13, 2010 at 12:02 PM, Selena Deckelmann <span dir="ltr"><<a href="mailto:selena@opensourcebridge.org">selena@opensourcebridge.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi folks,<br>
<br>
So, I heard through the grapevine that folks weren't happy with the<br>
coverage of python at OS Bridge.<br>
<br>
And I read through the thread. I have a suggestion at the bottom of<br>
this message that I hope you will consider, but first - here's a bunch<br>
of stuff I typed out that I hope you will read:<br>
<br>
First, let me say, I am totally excited that you care enough to read<br>
through our schedule and comment on it. I think in the future, we need<br>
to provide a way to look at suggested talks in a schedule-like<br>
interface so that folks can provide more feedback earlier on<br>
(especially before the committee makes selections!) regarding what<br>
they'd like to see. I say this because we posted the session list a<br>
while ago, and didn't receive any feedback about the lack of python.<br>
<br>
Second, it would have been greatly helpful to have had more people<br>
volunteering early on around the conference program and shaping of<br>
what the conference was going to become. We did have a member of the<br>
python community involved in talk selection, but because of scheduling<br>
(mostly my fault) we didn't really have as much interaction as I would<br>
have liked to have. Now, we're, of course, interested in day-of<br>
volunteers, but with only two weeks to go until the event.. it's tough<br>
to change the direction of a fast-moving train.<br>
<br>
Finally, the conference is definitely about cross-language<br>
collaboration, crazy and silly ideas, cultural hacking and what it<br>
means for us to be collaborating both in Portland, and around the<br>
world on code that we really care about. So, we don't emphasize any<br>
particular language. There was a fair bit of PHP this year - probably<br>
because the talks suggested by PHP folks seemed particularly<br>
interesting to the committee. We didn't actually get that many Ruby<br>
proposals, and while there were a lot of Perl proposals, I believe we<br>
only accepted one. We got a lot of functional language talks, and a<br>
ton of things involving infrastructure/operations/engineering. I think<br>
this reflects some of the problems that our peers are focused on right<br>
now. Or at least the folks that submitted talks. :)<br>
<br>
All that said, there are a couple openings for talks left. So here is<br>
what I propose:<br>
<br>
If this group would like to nominate a particular proposal for<br>
inclusion, I'm happy to do that. We reserve a few slots for<br>
last-minute changes, and so this is not out of protocol to do so. This<br>
all of course this depends on who is available, etc. But if you'd like<br>
to as a group organize something and recommend a talk, I will take<br>
your recommendation and add it to the schedule as soon as you're<br>
ready.<br>
<br>
-selena<br>
<font color="#888888"><br>
--<br>
<a href="http://chesnok.com/daily" target="_blank">http://chesnok.com/daily</a> - me<br>
_______________________________________________<br>
Portland mailing list<br>
<a href="mailto:Portland@python.org">Portland@python.org</a><br>
<a href="http://mail.python.org/mailman/listinfo/portland" target="_blank">http://mail.python.org/mailman/listinfo/portland</a><br>
</font></blockquote></div><br></div>