-
-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Abandoned #447
Comments
I'm still waiting for someone to clone this plugin and relaunch it on a new name... Or even better: maybe the original developer would be willing to transfer ownership to a new developer. |
We're going to resolve all the pressing issues over the coming month. Once they have been resolved we will revert the status of the plugin. |
Fantastic news, thanks a lot. |
That's nice to hear, but a lingering issue for me is: why no response until now? Was there an ownership change, or dev turnover? Was no one at Ether getting alerted to the Github comments? Can users feel confident that future showstopping issues like #432 won't hang out unresolved for more than 6 months? |
This is fantastic news, @alexjcollins! If there is anything I can help you with, please let me know and I will be happy to help. |
This is very important question that needs answering. What irritates me the most is the complete lack of communication and the sudden absence of developers from your side. I see the same devs are now working on merges again so what happend and can we trust it's not happening again in the future? 16k installs comes with a bit of responsibility IMO So I i'm eager to see the story here |
I'm joining this conversation first and foremost to thank Tam + Alex (and the team that put together this free plugin) for all their work. It's an invaluable tool that has saved me countless of hours in Craft projects. Yes, this plugin has a fairly large user base, but it is free, its code is available, and as such, it does not imply the people who originally developed it have any obligation whatsoever. Even if this plugin were abandoned, there would be no reason to bash the developers. We're all grown ups, we know what free means! We take our risks when using free products (free as in no liabilities attached). Why should we bash people that invested their own time so that we could save ours? I do hope this plugin sees a future, I'm using it in several projects, but as for every OSS project, there's a calculated risk in adopting it. And it's our risk, not the developers'. Lastly, I do appreciate being transparent and declaring that development and support is not feasible anymore. It gives us, as users, an opportunity to evaluate options. It's far worse when software goes into abandonware without much words from the developers. Just my 2c. Live well and happy ;-) |
Where did you get this from? I don't see any bashing in this topic, what do you mean by it? People simply questioning the future of this plugin. And it's a fair question. We all invested in this plugin somehow, so to abandon without any word out is not a very nice move to other devs, risk or not, it's not 1 person maintaining here. So when calling grown ups, grown ups can communicatie at the least right? :) |
@kevinmu17 It might be a misunderstanding due to the language you used: "What irritates me the most is the complete lack of communication and the sudden absence of developers from your side". They have no obligation to me, you or anyone who used this code they created, for free. They will be fully aware of their responsibilities and do not owe anyone any explanations. Maybe this would have been a better response: "I love this plug in and use it on my client sites. I appreciate the time you've spent on it in the past. It's a shame to see the development and support stopped recently. Please let us know if there is anything we can do to help?" Us developers have to support each other instead of being critical. PLUR. |
Description
So, word is out, this plugin has been abandoned.
Frustrating, to say the least. I mean, I get not having time for it at one point in time, but the communication about it could've been a lot better. Anyway, since this plugin has over 16.000 active installs, a lot of people will have some issues going forward. In what way can we uninstall the plugin and at minimum keep the current SEO data? I'm thinking migration scripts to simple fields, or migration scripts to a plugin f.e. like craft-seomatic.
Steps to reproduce
The text was updated successfully, but these errors were encountered: