<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div class="h5"><br>
</div></div>If I may recommend something is to try to inject talks in other track<br>
talking about Perl.<br>
So if there is a PostgreSQL track, inject a talk on something that<br>
connects Perl and Pg.<br>
etc.<br>
That will help us in getting out of the echo chamber even more than a<br>
separate dev room for Perl.<br>
<br>
regards<br>
<font color="#888888"> Gabor<br>
</font><div><div></div><div class="h5">___________</div></div><div class="h5"><br></div></blockquote><div> </div></div>I agree, but I think that can also be accomplished by focusing talks on certain off-Perl subjects within the Perl track dev room. <div>
<br></div><div>For instance, instead of a talk called "Using Test::More", call it "Test Driven Development", do a brief into on TDD, then demo Test::* packages. Or "Successful ORM", and base it on a DBIx::Class talk. That doesn't mean the "Perl6" talk should be called "The Future of Programming" -- I suppose there will be Perl developers who will see the "Perl6" title and will come by to check out what's up with Perl6. </div>
<div><br></div><div>Lame examples, but you get the idea. </div><div><br></div><div>cheers,</div><div><br></div><div>-rodrigo </div>