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

Sawyer X xsawyerx at gmail.com
Mon Dec 21 19:17:35 EST 2020

Speaking only for myself, I feel like it's always been a plan of mine to go
back to working on Dancer2 in earnest. The fact of the matter is I don't
get to use Dancer2 nowadays and this year had been... Hmm... catastrophic
in many ways. Then again, for many years of working on Dancer2, I wasn't
using it yet, so who knows. I still have multiple issues on my TODO list
involving Dancer2 and I've contributed two articles for the Advent Calendar
this year.

I'm hoping 2021 will be a better, more relaxed year and we could go back to
things we enjoy. To me, that would include hacking on Dancer2.

The set of accumulating tickets might warrant a fun hacking sprint. I would
love to host a day-long one over Zoom with breaks for talks. Dancer2 had
always been the most lovely community (or sub-community?) I've had the
pleasure to be in.

On Mon, Dec 21, 2020 at 7:50 PM Yanick Champoux <yanick at babyl.ca> wrote:

> On 2020-12-21 10:27 a.m., Juan José 'Peco' San Martín wrote:
> > I hope the Core developers will raise their hands if they feel they
> > can't spend enough time on the project. It's definitely not an easy year
> I am not actively working on Dancer these days, but I feel the need to
> raise my hand and just point out that
> 1. yes, it's been a heck of a crazy year. As far as I can say, anybody
> who managed to spend any meaningful period of time since March doing
> anything but rocking back and forth under a running shower are bloody
> heroes with more fortitude than I have.
> 2. every time the 'why the project isn't more active?' discussion comes
> around, I want to point out that all of the people working on Dancer (as
> far as I know) are doing it in their spare time. I know that often the
> question is not born out of malice, but for the people working on the
> project, it comes out as "oh, you're giving out stuff for free. But how
> come you're not giving more?"
> As I said, very often it's asked with the best intents. But it is
> soul-crushing. If I can recommend anything, in those scenarios I think
> it's more constructive to
> 1. explicitly thank the maintainers for the work they are already doing
> / have done in the past. You'd be surprised how often projects are met
> with long, looooooong stretches of absolute silence, only interspersed
> with occasionals "that's broken, fix it!".
> 2. is it a project your company rely on to make money? Then have them
> contribute.
> 3. thank the maintainers, for they are the little fairies making your
> lives easier.
> 4. if you are a developer who want to see something happens in the
> project, roll up your sleeves and pitch in. Sometimes it's... not
> possible because the bottleneck exists somewhere else. In those cases?
> :look right: ... :look left: :whisper: fork the project and go wild.
> 5. don't forget to thank the maintainers, if for no reason that there is
> a chance that the next time they roll their eyes to the sky and shout
> "why do I even bother?" to the heavens, this is the memory that will
> stop them from giving up and running to the desert to become hermits.
> *ahem* Soapbox speech ending. We can now resume our regular program.
> Oh yeah, I almost forgot:
> A big thanks to all the Dancer crew. I miss working on the project, and
> I miss you peeps. <3
> Seasonal joy,
> `/anick
> _______________________________________________
> 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/ae90d153/attachment.htm>

More information about the dancer-users mailing list