-
Notifications
You must be signed in to change notification settings - Fork 11
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
no activity -- Is this repro still maintained? #15
Comments
Great question, and I honestly don't have a good answer. Here's the history, I created this library as part of a different project when I was working at Domo (it was originally ported from the Python SDK). I asked the team maintaining the Java and Python SDKs if they'd like a Node version too since I had the start of one for my own project. That's where this library started, but I don't think there has ever been clear expectations on who the owner of the library is. I assumed it was the API team since they owned the Python and Java SDKs, and I think they assumed it was me because I got the ball rolling. Here's why I think there's someone better to be the main contributor for this library than me.
Perhaps @checketts can shed more light on the plans for this library. Will this have Domo representation to help the community keep this library going with enhancements to Domo APIs? Will there at least be someone who can review and approve PRs from the community? There are currently 2 open PRs that look to be valuable additions. Or does the README need to be updated with an |
I'll yield to @yunruiwatts or @rswingler for their analysis. I agree with @walexnelson that if no one is maintaining this library they should update the README appropriately. I'm sure community contributions will be reviewed and merged, just poke the corresponding PR/Issue. I don't think anyone was aware @walexnelson wasn't maintaining this anymore. |
And more than 1 year later, nothing changed :-( I wanted to use this library, but I guess it's not a good idea... |
Still no update. This seems to be a common thread among several of their repos... |
No description provided.
The text was updated successfully, but these errors were encountered: