Is Dyno still maintained?

[pierreis]

I see no activity on this repository since last February, and issues opened 3 months ago do not seem to be addressed.

Is Dyno still maintained by Mapbox, or will it soon be deprecated?

[AlJohri]

hey @mcwhittemore, just bumping this question. was wondering if this is still being maintained? I would love to submit a PR for #139 if you're still maintaining the repo

[mcwhittemore]

I don't think any one at Mapbox is actively working on it, but it is something we use a fair bit so I doubt we'd deprecate it.

[AlJohri]

@mcwhittemore cool, thanks- is there anyone at mapbox available to review PRs periodically? there's a couple open ones right now and I'd love to fix #139 as well.

I rolled my own bulk data transfer across aws accounts for now but I would love to rely on dyno instead.

[mcwhittemore]

I wouldn't bank on it. The team closest to this work is pretty deep on a few other things right now. They are aware of the PRs but are working to stay focused on that work. I'd treat any PR to this repo as a "someone might someday review". Sorry about that, I just want to make sure thats clear.

[rclark]

We still rely heavily on dyno internally, but we basically do not use the CLI tools anywhere. Our usage is first and foremost as a JS client alternative to aws-sdk-js.

Why do I bring this up as a challenge? Because issues and PRs that we've seen opened by the community tend to be focused on the CLI and backup/restore use-cases. We're not well-positioned to support that usage or review those PRs.

This was discussed some over in #136, but I wonder if we should make a more decisive. I would propose that we plan to remove the CLI functionality from this library. If someone else from the community would like to adopt and maintain it, we can help move the CLI code into another github organization. That CLI may continue to depend on @mapbox/dyno.