So I'm trying to think of how to aggregate all of these into a proper roadmap. We could add all of these as Github issues, or as Github wiki pages. My problem with doing it in issues is that it might conflate with bugs and feature requests. I'm actually not only interested in feature requests. I'm interesting in formalizing the direction Dancer2 is going in, and discussing how to get there. Eventually I want to end up with a document saying "This is where we're going and how". (for different values of "how" :) Thoughts? On Thu, Sep 11, 2014 at 11:18 PM, VinceW <info@vincew.net> wrote:
My 5cts
disclaimer: Just (about 18 months) getting my feet wet with Perl/D1 (coming from PHP/framework environment)
- mapping of current D1 modules against current D2 modules - priority listing of D1 modules needed to have in D2 - migration path from D1 -> D2
I would like to help the D1/D2 project. Having dev, git, linux experience, knowing a fraction of Perl (compared to others here on the list). Able to visit NL-PM and/or AmsterdamX.pm Willing to learn
Best, VinceW
On 09/11/2014 05:46 PM, Sawyer X wrote:
Hey everyone,
we're working on creating the Dancer2 roadmap. We need your help!
We want to design it with you, and we want to know: * What do you think should be on the roadmap for Dancer2? * What do you like to see being done? * What would you help with, if it was on the plan?
As the last item suggests, we're interesting in getting much more help with implementing this plan, once we have it written, so expect many "call to action"s. :)
Let's open a discussion!
_______________________________________________ dancer-users mailing listdancer-users@dancer.pmhttp://lists.preshweb.co.uk/mailman/listinfo/dancer-users
_______________________________________________ dancer-users mailing list dancer-users@dancer.pm http://lists.preshweb.co.uk/mailman/listinfo/dancer-users