-
Notifications
You must be signed in to change notification settings - Fork 102
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
Maintainers #118
Comments
I make use of this library and I'd be interested in helping! |
I'd be great to see some of those PRs being merged at some point. |
i'd like to help too :) |
We are using this as well. Happy to help.
Hi Paul! |
😁 Hi Peter! 👋 |
I wrote Syrus on May 4. He wrote back a few hours later and I responded, but I haven't heard anything since then. I'll follow up and see what he says! |
Happy to add maintainers! Thanks @paulmelnikow for reaching me personally. I just added you to the repo :) |
I noticed there are some alternate projects mentioned in #115. I hadn't noticed those before and at some point may investigate to see if one of those is farther along. Meanwhile, I'm happy to try to review and merge PRs. I merged the most popular unanswered PR #66 and left comments on a few more. I suggest we get a beta release out within a few days with the changes from #66, to get our release pipeline flowing. In short order we should also merge #112 or something similar. We should get the version number out of 0.x territory. Maybe we publish the next release as 1.0.0b0, and once we've merged #112, are confident in the beta, and have made all the breaking changes we want to make, in the short term, release it as 1.0.0? |
@davidshepherd7 has done a bunch of amazing work maintaining this library, both in his fork, and in carefully maintained PRs in made to this repo. (See #116 #112 #113.) @syrusakbary could you add him to this project too? |
@davidshepherd7 has been added and I now have publish access. Thanks @syrusakbary! |
This library appears to be stale at the minute - would @syrusakbary be interested in adding further maintainers, to work on the open PRs and issues?
The text was updated successfully, but these errors were encountered: