-
Notifications
You must be signed in to change notification settings - Fork 79
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
Is this a dead project? #30
Comments
any updates on this @alexcesaro ? |
Hi,
This is his brother. Alexandre won't be able to do any update to this
project. The library won't be maintained by him any more.
…On Wed, Aug 1, 2018 at 10:17 AM Dan Mordechay ***@***.***> wrote:
any updates on this @alexcesaro <https://github.com/alexcesaro> ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#30 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAyz3-0xhtQJtuSV_NCXIFuSSDn3GRWjks5uMWQxgaJpZM4Ozx1q>
.
|
Thanks for the update, I hope @alexcesaro is alright. |
@alexcesaro I would like to eventually contribute to the project. If I create a PR, is that going to be reviewed and eventually merged? |
Hey. Does it make sense to take this project to support? Have you migrated to another package? I can take this package for support if it is needed by someone. |
I have created a (backwards compatible) fork which I intend to maintain. I am using this anyway and needed an option to provide an arbitrary writer + an option to force inline flushing (to interface with external connection implementations). Not intended as a self-plug, just a FYI. If another fork gains traction and it's suitable for my needs I will merge it into mine and make a PR if necessary. |
I see that there has never been a merged PR and the last closed issue is over a year old.
Some of the issues ask simple questions such as #9 #14 #27
@alexcesaro are you actively maintaining this library any more?
The text was updated successfully, but these errors were encountered: