Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • (To those of you new to OSCON, I'm the program chair--I herd the committee that selects the talk and the buck stops with me over the quality or otherwise of the program)

    As Allison said, the talks in there were those that the program committee voted for. The methodology this year was to put all the proposals into a big pile, vote on those that were relevant to you, and accept those with the best average vote. There was a problem last year (ironically!) with the quality of talks in some of the tracks, so

    • Gnat, maybe this question should be on your journal, or a story on the front page, so more people can have the opportunity to answer?

      And I don't want to be presumptuous, but did you really mean that the conference organizers picked topics that were relevant to *them* personally? Because it seems to me that might be a rather flawed way of doing it.
      • I'll wait for the front-page story until I am in a position to do something with the answers I get--the Perl track this year is set, I can't throw it out and start again. So in November or December, let's ask that question as a story.

        But until then, I'd still love to know what you would consider good talks in a Perl track. I like to keep criticism constructive.

        The program chairs picked talks that they thought the audience would be interested in. Often there's overlap between what a program chair wants to see and what they think the audience wants to see. If you're saying, as I suspect you are, that Allison (as Perl 6 whip cracker and program chair) stacked the conference with her Perl 6 stuff, I think you're wrong. The majority of the talks have nothing to do with Perl 6, and I know she could fill days with Perl 6 talks if she chose to.

        I think that what you're seeing is caused by the lack of space, rather than editorial bias. Without a lot of room, we can't go deep into a lot of esoterica. Rest assured that, one way or another, this will be solved next year. We're already discussing internally how to change OSCON to ensure each technology gets a fair shake.


        • But until then, I'd still love to know what you would consider good talks in a Perl track. I like to keep criticism constructive.

          Well ... keep in mind, I was not so much saying that you should have done things differently. I told you some general notions I had, that I wanted more meaty topics, for example. But aside from my lack of interest in meaty topics, what you have there seems OK to me. I just want more.

          Or are you saying you didn't have more because there weren't enough good topics? If so, then I'
          • "I don't even really think I am criticizing, as much as I am bemoaning the loss of an institution. if market forces kill it off necessarily, that does not make its passing any less a sad event."

            I couldn't agree more. To me, the first TPC was where I first met people from the community and where the seeds were sown for Perl Mongers. The technical content was important, of course, but I see TPC1 as the beginning of the Perl community as we know it. On this, the 10th anniversary of that event, It would have be