Skip to content
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

Tether is end-of-life #214

Closed
davewasmer opened this issue May 29, 2018 · 7 comments
Closed

Tether is end-of-life #214

davewasmer opened this issue May 29, 2018 · 7 comments
Labels

Comments

@davewasmer
Copy link

It might be worth mentioning in the readme that Tether.js, the library that Shepherd uses for positioning popups, is end-of-life. Plus, Shepherd's future seems tenuous at best given Hubspot's apparent abandonment of open source maintenance.

@RobbieTheWagner
Copy link
Owner

Hi @davewasmer despite those issues, ember-shepherd is still the mostly highly rated tour library for Ember on https://emberobserver.com/categories/site-tours. Alternatives would be to write something 100% native Ember, but that could be quite a bit of work.

@davewasmer
Copy link
Author

Certainly, and I don't mean to knock any of the efforts of the ember-shepherd folks - happy to see it so active.

However, I think it could be worthwhile to at least include a note in the readme. Not explicitly deprecating ember-shepherd, but just calling out that the underlying libraries are either EOL or uncertain in their future.

I'm building out a tour feature for a client project and got pretty far down the road with ember-shepherd, only to discover that Tether is EOL. Client doesn't want to build on EOL'd tech (understandably), so now I've got to start over. Would have been good to know from the start.

@RobbieTheWagner
Copy link
Owner

@davewasmer I would argue that it's not really EOL though. It's stable and works great, and we've bolted on extra functionality here at ember-shepherd as well. Ember addons give us the opportunity to consume other JS libs and continue to support and improve upon them in our own way. ember-tether is also actively maintained https://github.com/yapplabs/ember-tether. I don't think it's fair to just abandon a bunch of really solid addons because HubSpot happens to not maintain some of the underlying libraries anymore. We could easily fork them, if there are any huge bugs or anything, but they mostly work really great.

@davewasmer
Copy link
Author

I would argue that it's not really EOL though. It's stable and works great

The Tether.js readme explicitly states that it is no longer maintained by Hubspot, and they recommend switching to Popper.js. The issue tracker has over 80 open issues, and after a cursory glance I'd estimate about half have no response whatsoever.

ember-tether is also actively maintained yapplabs/ember-tether

Which still depends on Tether.js though.

I don't think it's fair to just abandon a bunch of really solid addons because HubSpot happens to not maintain some of the underlying libraries anymore.

I think maybe I'm not being clear with my ask here - I apologize. I am definitely not recommending ember-shepherd be deprecated or abandoned in any way. I just thought it might be a good idea to mention in the readme that the underlying libraries are no longer maintained. If you have plans to fork and maintain them if and when that is needed, that would be a great note to include as well!


To reiterate - I'm super impressed by the work you and the other maintainers have done here. It's an awesome library, and I'm thankful for it's existence.

I just think it would be helpful to put a note in the readme describing the situation. I have a client who doesn't want to build on EOL'd tech, which is not entirely unreasonable, and I ended up burning a day and a half integrating ember-shepherd only to realize that I'll have to find something else. Including a note that could save others that kind of time (or more) in the future seems like a reasonable request (and I'm happy to PR it if you'd like).

If you still disagree, I'm guessing I won't be able to convince you otherwise; feel free to close this issue in that case.

Thanks again for all your hard work here (and elsewhere around Ember-land)!

@RobbieTheWagner
Copy link
Owner

I totally understand what you are saying @davewasmer, but I think my argument here is I disagree with your client arbitrarily not wanting to use ember-shepherd, when it is currently the best rated and most solid (to my knowledge) addon to use for this. I don't disagree with your desire for a warning, I just want to help change your mind to see what we can do to get you using the addon 😃 .

@RobbieTheWagner
Copy link
Owner

@davewasmer I was granted write access to the Shepherd repo, and I am actively talking with the folks at HubSpot about continuing Shepherd. It may be refactored to use popper. ember-shepherd and Shepherd will not be end of life, just FYI.

@davewasmer
Copy link
Author

Awesome news, glad to hear 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants