Skip to content

Conversation

@bytestream
Copy link
Collaborator

No description provided.

@bytestream bytestream marked this pull request as ready for review November 5, 2019 15:13
@bytestream
Copy link
Collaborator Author

@antonkomarev I intend to push several fixes which I have had on my fork. My fork has been used in production for 12months+ by several hundred people. Hoping you're willing to merge them so I can close my fork.

@antonkomarev
Copy link
Contributor

@bytestream core maintainer has returned recently. Pining @torrentalle for reviewing this PR.

@bytestream
Copy link
Collaborator Author

Any updates on this @torrentalle @antonkomarev

@bytestream
Copy link
Collaborator Author

@antonkomarev don't think he's back. What's it going to take to see done movement on this? I'm happy to help with this repo, I've been using it and submitting PRs for a long time.

@antonkomarev
Copy link
Contributor

antonkomarev commented Dec 24, 2019

@bytestream I've received email from him 30.01.2019 with words like "now I can retake this project contribute back again". I don't really know the exact situation. I'm just a user of this library, so I can't give you rights to merge PRs and don't have enough time to maintain this project by myself because not using it in any of my projects.
Sometimes making a fork is only an option to keep package alive.

@drjoju drjoju merged commit 368b19a into proengsoft:master Mar 13, 2020
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

Successfully merging this pull request may close these issues.

3 participants