Skip to content
This repository has been archived by the owner on Jan 20, 2024. It is now read-only.

Additional maintainer? #78

Closed
will-in-wi opened this issue Aug 4, 2017 · 4 comments
Closed

Additional maintainer? #78

will-in-wi opened this issue Aug 4, 2017 · 4 comments

Comments

@will-in-wi
Copy link

My company is switching to MarketingCloud and we are heavily depending on this SDK. I'd like to help maintain this gem, set up automated tests, and clean up the issue and PR queues. I am presently one of the maintainers of Capistrano, and have a number of years of experience maintaining Ruby applications.

Would any of the maintainers be willing to bring me on board with this?

Thanks!
~William Johnston
Software Engineer
Minnesota Public Radio/American Public Media

cc: @barberj (it looks like you've been doing work most recently, thanks!)

@barberj
Copy link
Contributor

barberj commented Aug 7, 2017

@will-in-wi I don't have any permissions in the salesforce-marketingcloud organization. Sorry

@wrs
Copy link

wrs commented Aug 17, 2018

One year later… We are also trying to bring up MarketingCloud and trying to decide whether to use this SDK, which seems to be abandoned. @amagar088, you did the last string of commits (ending in 2016) — are you still around? What is the plan here?

@will-in-wi and @barberj are you still involved with this code? Should we consider joining forces with like-minded customers and moving the center of gravity to another fork? There are a bunch of forks and a lot of them have useful looking tweaks and more major things like Savon compatibility fixes.

@will-in-wi
Copy link
Author

@wrs I've since changed jobs and no longer work with this gem. I'd be interested in helping maintain something, except that I now work for a competitor of marketing cloud. :)

@wrs
Copy link

wrs commented Aug 17, 2018

Ha! Fair enough. Opened #87 to ask the question.

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

No branches or pull requests

3 participants