Thoughts on status/roadmap?

[rubjo]

Hi,

Thanks for making this very nice library. I am considering using it in a project, but notice that it hasn't seen commits/PR merges in a year or so. So I wondered if you could share some thoughts about whether or not you consider it feature-complete, maintenance status, roadmap etc.

[vesper8]

I'm afraid author is MIA.. but package is very nice and extendable. I'm using it in production, as are many others clearly.. there isn't really anything better out there that I've found.

[Spacarar]

Agreed. Seems like he's abandoned this project for some time now. I too use this project in production and have resorted to self-hosting a forked version to patch issues we were experiencing. Specifically related to PR #426 and issues #423 and #425

edit: spelling

[antoniandre]

Hi guys, @rubjo, @vesper8, @Spacarar,
sorry I'm rather MIA on this library atm, but I'd really love to get things rolling for what is missing and/or not working as expected.
The thing is, it really takes a lot of time to dive in each PRs and issues and I am busy on other projects.
It frequently happens that I look into a PR and didn't merge because only a small portion of the problem is addressed and I don't have time to redo everything.

But I really appreciate your feedbacks all, and I am not dead yet. 🤘
So if someone wants to contribute in Vue Cal on a regular basis, I am happy to pair for some things, explain the codebase and where I left it, and discuss the next steps together. 🚀

If you're interested and and the codebase makes sense to you and doesn't scare you, reach out to me via email that you can find in the package.json. :)

If not, for now my priority is Wave UI.

❤️

[rubjo]

Big thanks to everyone for clarifying. I’m going ahead and will try this out for a small project - and will try to see if I can convince the higher powers that some financial support is in place for a useful open-source library like this if it is successful.

I haven’t actually come across any major bugs like the ones you refer to yet @Spacarar, I’m praying these won’t affect my use case. :)

I haven’t really looked much at the source codebase yet @antoniandre, so contributing to the code would maybe be out of my depths. If you find it helpful, though, I could probably go through and reply to some of the issues here - by the looks of them, several lack minimal reproductions of reported problems (and others seem very much more at home on Stack Overflow than on an issue tracker).

[antoniandre]

Thanks for your support.
Replying a few issues would definitely help, as well as classifying them with labels, and having financial support for more time investment.
I've just updated a few things - dependencies, vulnerabilities, and merged a couple of straightforward PRs.
the rest requires more time.
And for the cheering part, I will most likely work on this codebase again this year.

[rubjo]

I've gone ahead and commented and asked for repro / more info on a lot of the issues.

Other issues are clearly inactive / missing responses after you have asked for more info, and should just be closed. I wasn't able to close off outdated ones or start organising the issues with labels.

TBH I would just close most of the ones not providing repros or not having seen any activity for a year or two.

And with Vue 3 now being the default, I think I would actually consider only focusing on the next codebase moving forward.

[vesper8]

I'm maintaining a dozen projects built on Vue 2 with no intent, desire, or reason really, to upgrade to Vue 3. Vue 3 may be the default for new projects (which is arguable, but not looking to argue it here) but Vue 2 remains by far the most deployed and maintained version out in the wild. It's entirely up to you whether you want to only focus on the next branch but I think that would be unfortunate and would likely lead to other contributors backporting your changes into the Vue 2 branch.

Overall I've found your package to be quite stable and mostly feature-complete. The one feature request that would be awesome to have in the future, which seems to be quite involving, is the horizontal timeline: https://github.com/antoniandre/vue-cal/issues/87

I'm happy to hear you may find some time to work on this in the coming year, and thank you again for your contribution.

I also don't think this issue should have been closed : ) Perhaps it should be pinned instead.

[rubjo]

I feel your reaction @vesper8 :) It was a suggestion on how to move forward to an author who has made something great, but has limited time, like anyone else. Maybe leaving other contributors backporting the changes into the Vue 2 branch could actually free up time for @antoniandre to make one version more stable, I don't know.

I agree that #87 sounds like a mammoth task, one that transforms the view completely and is perhaps better served by other libraries (?)

I can always reopen this for a while, but a roadmap or similar is probably best organised by the author himself and in a different way than a long-winded issue.

[antoniandre]

Hey guys!
Thanks for the help @rubjo, I'll close a few issues shortly, at least all the no-repro.
I understand your point @vesper8, and when I add more features/bug fixes, I will also add them in the vue 2 branch.
In a near future though, vue-cal will also default to the next branch to follow vue 3 as vue-cal depends on it.
But practically for users, it will only change how you install from npm.

When I'm back in the codebase, I will focus on smaller features first and refactoring a few things.
Meantime, anybody if you want to contribute, it's very appreciated. You can submit well-tested PRs that take all the cases in consideration, and I'll merge in if it looks complete. :)
@rubjo, if you wish to help things moving on, you can have a stab at #462 which is probably very easy to fix. :)

[antoniandre]

Closing this issue as I have already rebooted the project.
I don't have full time, but I will do a few improvements and bug fixes.