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!
One of my big projects right now involves streaming a live webcam into an HTML5 video stream, which means it needs to stream a filehandle. I have a bug in the system to implement this in send_file(): https://github.com/PerlDancer/Dancer2/issues/659 I ended up backporting to Dancer1 because of hitting this. Even better would be to have a simple function call that takes a filehandle directly and streams it without needed to specify callbacks. A smaller issue is to have an easy way to disable splat behavior. I'm reimplementing an existing REST API that has some literal '*' in many of the calls. With things on Dancer1, I was able to get it to work with a regex match, though that didn't seem to work when I tried it on Dancer2. Either way, a regex seems like an unnecessarily complicated way of solving this. Thanks, Timm On Thu, Sep 11, 2014 at 10:46 AM, Sawyer X <xsawyerx@gmail.com> 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 list dancer-users@dancer.pm http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
I should add that this is my first Real Dancer Project, so maybe I'm just missing something. On Thu, Sep 11, 2014 at 12:23 PM, Timm Murray <tmurray@wumpus-cave.net> wrote:
One of my big projects right now involves streaming a live webcam into an HTML5 video stream, which means it needs to stream a filehandle. I have a bug in the system to implement this in send_file():
https://github.com/PerlDancer/Dancer2/issues/659
I ended up backporting to Dancer1 because of hitting this.
Even better would be to have a simple function call that takes a filehandle directly and streams it without needed to specify callbacks.
A smaller issue is to have an easy way to disable splat behavior. I'm reimplementing an existing REST API that has some literal '*' in many of the calls. With things on Dancer1, I was able to get it to work with a regex match, though that didn't seem to work when I tried it on Dancer2. Either way, a regex seems like an unnecessarily complicated way of solving this.
Thanks, Timm
On Thu, Sep 11, 2014 at 10:46 AM, Sawyer X <xsawyerx@gmail.com> 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 list dancer-users@dancer.pm http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
Can multiple Dancer2 applications launched in the same Starman already? If not, then that would be an important one. IMHO. Gabor
A style guide (mostly for plugins). I'm a big fan of johnpapa's AngularJS style guide <https://github.com/johnpapa/angularjs-styleguide>. I think it would benefit mostly plugins development. If you take a look at 3 major plugins source: Database <https://metacpan.org/source/AMBS/Dancer2-Plugin-Database-2.10/lib/Dancer2/Plugin/Database.pm>, REST <https://metacpan.org/source/YANICK/Dancer2-Plugin-REST-0.24/lib/Dancer2/Plugin/REST.pm> and DBIC <https://metacpan.org/source/IRONCAMEL/Dancer2-Plugin-DBIC-0.0006/lib/Dancer2/Plugin/DBIC.pm> . 3 different ways to register keywords ( sub anonymous vs ref ). Different version and abstract declarations. die vs croak. Show keyword declarations at top or bottom? Maybe a style guide on how to decouple business logic from dancer routes (file splitting, modules for business). But I understand that style guide's are highly opinionated and may not suit every team or project. But a general one would be better than nothing in my opinion. Or maybe a style guide has nothing to do with Dancer2 core... On Thu, Sep 11, 2014 at 1:28 PM, Gabor Szabo <gabor@szabgab.com> wrote:
Can multiple Dancer2 applications launched in the same Starman already? If not, then that would be an important one. IMHO.
Gabor
_______________________________________________ dancer-users mailing list dancer-users@dancer.pm http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
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 list dancer-users@dancer.pm http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
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
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?
I think GH Wiki is the place to go. Easier to collaborate as opposed to issues as well. Regards Racke -- Perl and Dancer Development Visit our Perl::Dancer conference 2014: http://act.perl.dance/
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@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
_______________________________________________ dancer-users mailing list dancer-users@dancer.pm http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
Hi all, I would like D2 achieve the goal: "D2 ready for production... in any scenario". IMHO, these could be the 4 sub-goals: 1) D2 vs D1: Develop features/plugins that are in D1 but missing in D2. 2) D2 as a solid rock: Close as many issues (bugs) as possible. 3) D2 enhancements: integration. There is not need to create the specific plugin for each case, just the documentation/tutorial on how to connect your Dancer app with.. 4) D2 homepage: www.dancer.org seems to talk about D1. What about www.perldancer2.org or join both on the same site? I could buy the domain and dedicate space for webhosting. Happy hacking, Peco 2014-09-12 10:30 GMT+02:00 VinceW <info@vincew.net>:
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@vincew.net> <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 listdancer-users@dancer.pmhttp://lists.preshweb.co.uk/mailman/listinfo/dancer-users
_______________________________________________ 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
4) I would say keep it on -1- site. For end-users more logical, for maintenance too. Also info about differences, upgrade paths etc are more logical over there. Best, VinceW On 09/12/2014 10:34 AM, Juan José 'Peco' San Martín wrote:
Hi all,
I would like D2 achieve the goal: "D2 ready for production... in any scenario".
IMHO, these could be the 4 sub-goals: 1) D2 vs D1: Develop features/plugins that are in D1 but missing in D2. 2) D2 as a solid rock: Close as many issues (bugs) as possible. 3) D2 enhancements: integration. There is not need to create the specific plugin for each case, just the documentation/tutorial on how to connect your Dancer app with.. 4) D2 homepage: www.dancer.org seems to talk about D1. What about www.perldancer2.org or join both on the same site? I could buy the domain and dedicate space for webhosting.
Happy hacking,
Peco
2014-09-12 10:30 GMT+02:00 VinceW <info@vincew.net>:
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@vincew.net> <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 listdancer-users@dancer.pmhttp://lists.preshweb.co.uk/mailman/listinfo/dancer-users
_______________________________________________ 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
_______________________________________________ dancer-users mailing list dancer-users@dancer.pm http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
While going forward, implementing new features is good, we should not forget about the documentation as well. On Fri, Sep 12, 2014 at 10:59 AM, VinceW <info@vincew.net> wrote:
4) I would say keep it on -1- site. For end-users more logical, for maintenance too. Also info about differences, upgrade paths etc are more logical over there.
Best, VinceW
On 09/12/2014 10:34 AM, Juan José 'Peco' San Martín wrote:
Hi all,
I would like D2 achieve the goal: "D2 ready for production... in any scenario".
IMHO, these could be the 4 sub-goals: 1) D2 vs D1: Develop features/plugins that are in D1 but missing in D2. 2) D2 as a solid rock: Close as many issues (bugs) as possible. 3) D2 enhancements: integration. There is not need to create the specific plugin for each case, just the documentation/tutorial on how to connect your Dancer app with.. 4) D2 homepage: www.dancer.org seems to talk about D1. What aboutwww.perldancer2.org or join both on the same site? I could buy the domain and dedicate space for webhosting.
Happy hacking,
Peco
2014-09-12 10:30 GMT+02:00 VinceW <info@vincew.net> <info@vincew.net>:
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> <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@vincew.net> <info@vincew.net> <info@vincew.net> <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 listdancer-users@dancer.pmhttp://lists.preshweb.co.uk/mailman/listinfo/dancer-users
_______________________________________________ dancer-users mailing listdancer-users@dancer.pmhttp://lists.preshweb.co.uk/mailman/listinfo/dancer-users
_______________________________________________ dancer-users mailing listdancer-users@dancer.pmhttp://lists.preshweb.co.uk/mailman/listinfo/dancer-users
_______________________________________________ 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
participants (8)
-
Gabor Szabo -
Jacques Lareau -
Juan José 'Peco' San Martín -
Kovács Dávid [ Davs ] -
Sawyer X -
Stefan Hornburg (Racke) -
Timm Murray -
VinceW