[dancer-users] Development of Dancer stalling? What to do?

[Russell Jenkins]

While I have no immediate answers, everyone is aware that the last 9+ 
months, and possibly the year ahead are somewhat unprecedented.

Personally, in 2020 I've had a significant transition in working 
conditions plus supporting schooling children from home for a decent 
chunk of the year, yet I consider myself one of the lucky ones. As a 
core developer the amount of time I could contribute has been severely 
impacted. I've contributed where I can, checked in on, poked and prodded 
other core devs where I thought needed.


While I'll gracelessly accept the (virtual) golden dancer award (thanks 
@cromedome!), I'll happy to acknowledge there is more to be done. But 
this is not the time to jump to conclusions that Dancer2 development is 
stalled, perl is dead, or whatever phrase is the flavor for today. It's 
always been said that issues and pull requests are always welcome. The 
core team will get to them as time allows. Recent PR's have been 
approved by two core devs ready for merge. If something has stalled, a 
gentle prod or bump can go a long way too.


Advent driven development is also a thing, expect the reported numbers 
to change soon. I'd better go write up my advent article...


All the best for the silly season.

   Russell @veryrusty Jenkins.


ps. The definite list of keywords is in Dancer2::Core::DSL.


On 21/12/20 5:14 pm, Gabor Szabo wrote:
> Hi,
>
> as I am working on the Perl Dancer video course I need to look up lots 
> of things in the documentation on https://metacpan.org/release/Dancer2 
> <https://metacpan.org/release/Dancer2> and many times I feel either 
> that it is difficult to find what I was looking for
>
> For example looking for the full list of words in the DSL:
> I clicked on both links saying DSL, neither of them had the list, nor 
> a link to the manual
> where I findall found it:
> https://metacpan.org/pod/distribution/Dancer2/lib/Dancer2/Manual.pod#DSL-KEYWORDS 
> <https://metacpan.org/pod/distribution/Dancer2/lib/Dancer2/Manual.pod#DSL-KEYWORDS>
>
> Another thing I was looking for is the list of types one can use out 
> of the box to describe the routes. I could not find it.
>
> -------------------------------------
>
> It is frustrating, but this is open source, I can help improve it, right?
>
> I thought I'll open a ticket, maybe even send a pull-request.
>
> Looked at https://github.com/PerlDancer/Dancer2/ 
> <https://github.com/PerlDancer/Dancer2/>
>
> and this made me even more frustrated. There are 110 open issues and 
> 32 open pull-request. That's 32 things some people have worked on and 
> have not been integrated.
>
> (If you like, you can compare the numbers with
> Mojolicious https://github.com/mojolicious/mojo 
> <https://github.com/mojolicious/mojo> 47 3
> Flask https://github.com/pallets/flask 
> <https://github.com/pallets/flask> 18 4
>
> You can also look at the commit history and you see there was hardly 
> any activity recently.
>
> I keep recording the course, but I feel reluctant to open issues or 
> work on pull-request because I don't want to waste my time on 
> something where the chances of integration seem to be so low.
>
> -------------------------------------------
>
> Why has the development slowed down? How could it be fixed?
> Have the core developers (almost completely) lost interest?
> Do they lack the time?
> Could companies that use Dancer help financially?
> Could new people step up to become core developers?
>
> regards
>     Gabor
>
>
> _______________________________________________
> dancer-users mailing list
> dancer-users at lists.preshweb.co.uk
> https://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/20201221/70c18b7d/attachment.htm>