<div id="reply-content">
<br>
</div>
<div id="9C85D5E8EC4D46DF8063F8D80A7F500C"></div>
<p style="color: #A0A0A8;">Le jeudi 27 décembre 2012 à 13:34, David Precious a écrit :</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<div id="quoted-message-content"><div><div>On Wed, 26 Dec 2012 19:00:21 +0100 (CET)</div><div>Celogeek <me@celogeek.com> wrote:</div><div><br></div><blockquote type="cite"><div><div>Hi, I have start hacking Dancer2 project. </div><div><br></div><div>I have multiple question : </div><div><br></div><div>- I know people are busy, but how long take a patch to be merge after</div><div>2 validations and 3 weeks still waiting ? I'm waiting to see if the</div><div>project is still active to add futher patches. </div></div></blockquote><div><br></div><div>It is active.</div><div><br></div><div>Assuming you mean PR 132 (using XS versions of a couple of modules for</div><div>a slight speed improvement), I would have merged it a lot quicker were</div><div>it adding new useful features or fixing a troublesome bug, but as it's</div><div>simply a minor performance improvement, I haven't felt the need to give</div><div>up too much time to review it yet. I also would have merged it a lot</div><div>sooner if it would merge cleanly through GitHub, but it looks like it's</div><div>going to conflict.</div><div><br></div><blockquote type="cite"><div><div>- I want to update my Dancer::Plugins::Redis, but I'm a little bit</div><div>lost on the right way to do it. How to be compatible with v1 and v2 ? </div></div></blockquote><div><br></div><div>See any of the modules which have already been updated - there's only a</div><div>few minor changes usually, activated by checking dancer_version (which</div><div>is another discussion).</div><div><br></div><blockquote type="cite"><div>- Is they an equivalent website as perldancer.org for perldancer2 ? </div></blockquote><div><br></div><div>It's the same project, so will have the same website (it'll be updated</div><div>when the first stable release of Dancer2 is made, I'm sure).</div><div><br></div><div><br></div><blockquote type="cite"><div><div>- I have start writing App::Dancer2 (already push on cpan), based on</div><div>the Dancer2 mainline git repository example. Is they a doc somewhere</div><div>to do stuff more complicated ? </div></div></blockquote><div><br></div><div>What kind of "stuff"?</div><div><br></div><blockquote type="cite"><div>- is they a list of Dancer2 already patched module ? </div></blockquote><div><br></div><div>I don't think there's a definitive list yet - if you try loading a</div><div>plugin that hasn't been updated to support Dancer2, though, Dancer2</div><div>will tell you.</div><div><br></div><blockquote type="cite"><div><div>I think a website like " https://www.djangoproject.com/" or "</div><div>http://rubyonrails.org/" or "http://perldancer.org" could be great to</div><div>speed up the passage from v1 to v2. Having a good tutorial to start a</div><div>Dancer2 project, and to create some awesome Dancer2::Plugins is</div><div>essential. A place where all of this can be found. </div></div></blockquote><div><br></div><div>Any contributions would be very welcome. I'm not entirely sure of the</div><div>relevance of Django or RoR, unless you mean there are parts of their</div><div>website you think are good and could be used as inspiration - if so,</div><div>feel free to point at those parts :)</div><div><br></div><div><br></div><blockquote type="cite"><div><div>What do you think ? </div><div><br></div><div>I was thinking of a kind of wordpress website (like mine :)</div><div>http://blog.celogeek.com ) to push our discover, our tutorial ... Any</div><div>contributor could push their discover. </div></div></blockquote><div><br></div><div>I've been mulling the idea of a project blog a few times - might be</div><div>worth consideration.</div></div></div></blockquote><div><br></div><div>That remains me of the Dancer blog, which we started months ( years ? ) ago. It should be still active, it's using the github pages feature, so creating a new blog post is as simple as committing and pushing. </div><div><br></div><div>Maybe it would be useful to resurrect it and use it as a follow up of the advent calendar: people can provide article, volunteers can write up weekly newsletters and so on. It's only limited by the amount o volunteers :)</div><div> </div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;"><div id="quoted-message-content"><div><div><br></div><div>Proper tutorial stuff, though, I think should be written up as POD</div><div>(Dancer::Tutorial, Dancer::Tutorial::*) and shipped with Dancer itself.</div><blockquote type="cite"><div><div>Something : </div><div><br></div><div>Starting a new Dancer2 project </div></div></blockquote><div><br></div><div>We should have a bootstrapping script ready to go, so that will be</div><div>pretty simple, but of course usage of that script should be documented</div><div>in the basic tutorial.</div><div><br></div><blockquote type="cite"><div>Starting a new Dancer2 Plugins</div></blockquote><div><br></div><div>Indeed, a guide to writing plugins could be valuable. It should be</div><div>pretty simple though, so could just be a section in the docs for</div><div>Dancer::Plugin (with references to it within the tutorial, etc).</div><blockquote type="cite"><div>How to upgrade your Dancer1 plugins to be compatible with Dancer2 </div></blockquote><div><br></div><div>Yeah, a guide on that would be good; I think there's already some</div><div>content around for that.</div><div><br></div><blockquote type="cite"><div>How to create a Dancer1 / Dancer2 plugin </div></blockquote><div><br></div><div>That should be merged with the "Starting a new Dancer2 plugin" above, I</div><div>think.</div><div><br></div><blockquote type="cite"><div>Hacking Dancer2, how to post your patches </div></blockquote><div><br></div><div>That'll be Dancer::Development when it's ported to D2.</div><div><br></div><blockquote type="cite"><div>Our IRC </div></blockquote><div><br></div><div>That's already featured on the website and in documentation etc.</div><div><br></div><div><br></div><blockquote type="cite"><div><div>If anyone is interested, I can work on it and take the</div><div>perldancer2.org domains if needs. </div></div></blockquote><div>Thanks for the offer but we're fine for hosting and site infrastructure</div><div>- contributions towards the documentation as discussed above would be</div><div> very gratefully received though!</div><div><br></div><div>Cheers!</div><div><br></div><div>-- </div><div>David Precious ("bigpresh") <davidp@preshweb.co.uk></div><div>http://www.preshweb.co.uk/ www.preshweb.co.uk/twitter</div><div>www.preshweb.co.uk/linkedin www.preshweb.co.uk/facebook</div><div>www.preshweb.co.uk/cpan www.preshweb.co.uk/github</div><div><br></div><div><br></div><div>_______________________________________________</div><div>dancer-users mailing list</div><div>dancer-users@dancer.pm</div><div>http://lists.preshweb.co.uk/mailman/listinfo/dancer-users</div></div></div>
</blockquote>
<div>
<br>
</div>