Maintainer/transfer

[RobbieTheWagner]

@b-ash @adamschwartz @zackbloom I wrote and maintain https://github.com/shipshapecode/ember-shepherd and it still remains the best rated addon for site tours, despite the issues piling up here, so I would hate to see it die. If HubSpot is not interested in maintaining Shepherd anymore, would you be open to transferring ownership to my company?

[FranDias]

Yeah, we're interested in that 😄

[FranDias]

You have write perms, would it be better to add a team?

[RobbieTheWagner]

Thanks @FranDias! Does HubSpot still use Shepherd at all or have an interest in the future direction? I just commented on the PR converting from tether to popper, which I think might be the best path forward. Did you want to keep the repo under the HubSpot org or transfer it to me?

[FranDias]

What we internally use has differed (a react implementation) than what's here but that also hasn't seen too many changes over the past few months.

@Phoenixmatrix @also Thoughts on the give write vs transfer?

[Phoenixmatrix]

I'd probably loop in @TrevorBurnham on this one, as Im pretty sure we still rely on Shepherd internally.

[TrevorBurnham]

@Phoenixmatrix Yes, we do still use Shepherd internally, but I'd be delighted to see this project go to an active maintainer. I think transfer would be preferable, since no one at HubSpot actively works on Shepherd anymore.

[RobbieTheWagner]

@TrevorBurnham would you guys be in favor of moving to popper as well? I think that may be the best path forward, since tether has been recommending to use popper now anyway.

[TrevorBurnham]

@rwwagner90 I'd have no objection. We still use Tether internally at HubSpot, but Popper is the better project at this point.

[FranDias]

Github only allows for transferring org repos to a member.

I'm transferring to me then transferring to @rwwagner90. Should be done in a few minutes.

[FranDias]

Transfer request initiated/completed.

[RobbieTheWagner]

Awesome, thanks guys! I will proceed with the popper conversion and other updates in the coming weeks.

[RobbieTheWagner]

@FranDias do you know what was used to generate the docs and push to gh-pages?

[FranDias]

@geekjuice @b-ash would know what jade template library they were using to build the docs …5 years ago?

[geekjuice]

we used an internal doc building library that is very outdated at this point. while we will happily rebuild docs when needed, i do wonder if it'll be easier to just use one of the many doc building tools out there instead now since the one we used was fairly brittle 😬

[RobbieTheWagner]

Sure thing, we can convert to something else. If it were something open source and easy to use, I would use it, but otherwise we can work on rebuilding.

[RobbieTheWagner]

@FranDias @geekjuice could I get permissions on npm as well and/or could you just go ahead and deprecate tether-shepherd and point to shepherd.js? I just released as shepherd.js now. https://www.npmjs.com/package/shepherd.js