Open phiberber opened 2 years ago
phiberber
commented
2 years ago This issue and its proposal is also valid to the VueSax 3 library: https://github.com/lusaxweb/vuesax/
There is a lot of issues there unanswered, where people just gave up: https://github.com/lusaxweb/vuesax/issues/959#issuecomment-781841865 https://github.com/lusaxweb/vuesax/issues/770 https://github.com/lusaxweb/vuesax/issues/34 https://github.com/lusaxweb/vuesax/issues/1000.
phiberber
commented
2 years ago Must also say that the VueSax discord is full of Discord bots who lead people in losing their accounts, there is basically no moderation there and people just do what they want, must be an anarchy server.
Be careful when clicking links in the VueSax Discord.
phiberber
commented
2 years ago For the ones looking still for an alternative fork or branch:
VueSax 4: https://github.com/shtelzerartem/vuesax-next VueSax 3: https://github.com/Tofandel/fixed-vuesax
Thanks for the community who, even when unknown, keep this project "alive".
(These forks are not fully trusted and have a poor documentation, may have commercial-specific features that you may not want)
lk77
commented
2 years ago Hello,
i made a fork of original Vuesax package (not vuesax-next) that is supporting Vue 3 :
đđťď¸ Hi VueSax community.
I am asking here to create a warning, so people can see that this repository is currently unmaintained.
A lot of people have been asking the same question both in Discord and Github: "Is this project dead?"; the answer for it is probably yes. Even though there's still a lot of people that have been trying to use this project, without knowing it is unmaintained.
Where do these people come from, you may ask? Probably the VueSax website, that does NOT have any warning about it being unmaintained...
For the ones who still think that this repository may come back one day, @luisDanielRoviraContreras himself has said that "most likely" he's going to create a new v4 branch and continue the work there (Maybe this https://github.com/Vuesax/vuesax)
We also know that this "continuation" may not even happen, as Luis has had Commercial Works for a long time already.
Now how harmful is this problem? Well, probably 1 week of anyone that tries to use this project in a production environment, trying to fix its components, and there is a lot to fix here: https://github.com/lusaxweb/vuesax-next/issues/129#issuecomment-835407007.
Even the Nuxt team itself has claimed this repository as unmaintained, you can see this at https://github.com/nuxt/create-nuxt-app/pull/795 and https://github.com/nuxt/create-nuxt-app/issues/779.
My proposal is to do something like Vue Native has done with both their website and github repository.
These are all the issues related to the same issue: https://github.com/lusaxweb/vuesax-next/issues/222 https://github.com/lusaxweb/vuesax-next/issues/169 https://github.com/lusaxweb/vuesax-next/issues/161 https://github.com/lusaxweb/vuesax-next/issues/147 https://github.com/lusaxweb/vuesax-next/issues/129 https://github.com/lusaxweb/vuesax-next/issues/80.
We also have a lot of Discord messages only regarding this issue, here are some: joshwcorbett deleted user passenger mikias kowalskijr darkmode sneakypeaky.
Now @luisDanielRoviraContreras, if you are reading this, I am proposing myself to create a Pull Request with the unmaintained warning both in the documentation and in the Readme, 10 minutes of your time is less than 1 week of probably 50 people.
That's a coffee break! âď¸