[dancer-users] Dancer2 Roadmap - your help needed!

[VinceW]

I suggest to have the (pre) final roadmap in the wiki (for instance 
ROADMAP-2015)

on the other hand .... , discussions on topics to go in the roadmap, are 
best placed into the issue queu because
- easy adding comments/reactions to it
- keeping history of the discussion
- closing of the discussion

To organize this we could use the extended search function for issues, 
mentioning:

ROADMAP in:title 
<https://github.com/search?q=warning+in%3Atitle&type=Issues>
    Matches issues with ROADMAP in their title.

one could even decide to differentiate this more to ROADMAP-2015

so when in a few years a new roadmap has to be created, that title tag 
could be ROADMAP-2017

Best,
VinceW



On 09/12/2014 10:16 AM, Sawyer X wrote:
> 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 at 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 at dancer.pmhttp://lists.preshweb.co.uk/mailman/listinfo/dancer-users
>>
>>
>>
>> _______________________________________________
>> dancer-users mailing list
>> dancer-users at dancer.pm
>> http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
>>
>>
>
>
> _______________________________________________
> dancer-users mailing list
> dancer-users at dancer.pm
> http://lists.preshweb.co.uk/mailman/listinfo/dancer-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.preshweb.co.uk/pipermail/dancer-users/attachments/20140912/e4566b7b/attachment.html>