Stories
Slash Boxes
Comments
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.
 Full
 Abbreviated
 Hidden
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

    • To satisfy my curiosity, what topics would you like to see?

      It might be helpful to stimulate discussion if you posted a list of the submission titles ? (no names, and maybe scrubbing a few titles to protect the innocent).

      Much of the following is general to OSCON as a whole...

      I'd certainly like to see more useable content. PBP and HOP are swell and all, but I suspect most managers will find it hard to justify the expense of sending an employee to Portland for a week - including conference fees, trav

      • It might be helpful to stimulate discussion if you posted a list of the submission titles ? (no names, and maybe scrubbing a few titles to protect the innocent).

        No, that'd be figuring out what you wanted from what you were offered. But a key part of being program chair of a track is figuring out what you should have and reaching out to get it. So I really want to hear what you would want to see in a Perl track. That way we can get it next year. (In general, having this discussion buried deep in Pudge's comments doesn't work--we'll do it as part of a front-page story in November or December)

        Thinking about how to structure that questionnaire in Nov/Dec, I guess the questions would be something like:

        • Which elements of which CPAN projects would you like to see talks on? (e.g., not just "Catalyst" but "Scaling Catalyst" or "Debugging Catalyst" or "Writing XYZ Plugins for Catalyst")
        • Which elements of pure Perl programming would you like to see talks on?
        • Which business problems would you like to see sessions about, in the context of "how to solve this problem with Perl"?
        • What kinds of case studies in general would you like to hear about?

        That would structure the questions so as to give useful immediate actionable answers.

        Thoughts?

        --Nat

        • It might be helpful to stimulate discussion if you posted a list of the submission titles ? (no names, and maybe scrubbing a few titles to protect the innocent).

          No, that'd be figuring out what you wanted from what you were offered.

          Correction: that'd be what I wasn't offered.

          Like the Pacific Ocean, Perl is big, deep, and diverse. Alas, much of what OSCON06 offers is of the "Isn't water great ?" variety. I (and I suspect many others) don't know what we don't know. We don't have the cycles to scan ev