Skip to content
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

Closed
ghost opened this issue Apr 24, 2020 · 10 comments
Closed

Maintainers #118

ghost opened this issue Apr 24, 2020 · 10 comments

Comments

@ghost
Copy link

ghost commented Apr 24, 2020

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?

@paulmelnikow
Copy link
Collaborator

I make use of this library and I'd be interested in helping!

@versae
Copy link
Contributor

versae commented May 4, 2020

I'd be great to see some of those PRs being merged at some point.

@gustavopp93
Copy link

i'd like to help too :)

@chenliu0831
Copy link

We are using this as well. Happy to help.

I make use of this library and I'd be interested in helping!

Hi Paul!

@paulmelnikow
Copy link
Collaborator

Hi Paul!

😁 Hi Peter! 👋

@paulmelnikow
Copy link
Collaborator

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!

@syrusakbary
Copy link
Owner

Happy to add maintainers!

Thanks @paulmelnikow for reaching me personally. I just added you to the repo :)

@paulmelnikow
Copy link
Collaborator

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?

@paulmelnikow
Copy link
Collaborator

@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?

@paulmelnikow
Copy link
Collaborator

@davidshepherd7 has been added and I now have publish access. Thanks @syrusakbary!

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

No branches or pull requests

5 participants