-
Notifications
You must be signed in to change notification settings - Fork 100
PROJECT STATUS - PLEASE READ #205
Comments
Ouch... I'm sorry to hear that, @vcabbage. You have done a great job with your work on this library. Thank you so much for working on this!! Have you thought about where you would like to see this project land? Perhaps, as a donation to one of the OSS foundations? |
@devigned Thank you for the kind words and your numerous contributions. I haven't thought too much about where it ends up other than figuring that the MIT licensing allows someone else to pick it up relatively easy. I don't know much about the OSS foundations. |
Sorry to hear that - I am eager to find a pure Go replacement for Apache's electron and this is the most promising I've seen. Well done on a clear, performant implementation of a complicated protocol and effective use of Go concurrency to provide session and link concurrency. |
Sorry to hear that, Thank you so much for working on this. This library is the only great one for AMQP1.0 implementation of Go and it has running several month at production environment. |
Thanks again to everyone. This repo should now be considered read only. I'm going to leave it un-archived for a little longer on the chance that someone does want to share a fork or other project they intend to maintain. |
Looks like this fork has been started: https://github.com/Azure/go-amqp Hope the plan is to have it maintained long-term. |
It's become apparent that I don't have the time to properly maintain this library anymore. I don't want to be holding up continued development and feel that I should make room for a fork or alternative library run by those that do have the time to maintain it.
I'm going to stop accepting contributions/addressing issues with the intent to archive the repo eventually. I will merge existing PRs that are near ready if their authors still wish them to be.
If anyone does decide to fork or start a different project please feel free to post here.
Thank you to everyone who has contributed.
The text was updated successfully, but these errors were encountered: