⚠️ Call for Maintainers

[worg]

Over the past few months, I've been navigating through some challenging personal circumstances that have significantly limited my availability. Alongside these personal matters, my schedule has become increasingly packed, making it difficult for me to dedicate the time and energy that the library deserves.
To keep this project alive, we are looking for someone to take over the maintainer role. Ideally, this person will have a proven track record of contributions to open-source software projects. (no one wants another XZ utils fiasco).
If you are interested in becoming a maintainer for this project, please feel free to comment below and express your interest.

[singh-harveer]

Hi @worg,

I hope you are doing well.

I am an engineer with 6+ years of experience in Golang, and I would like to maintain or contribute to this project.

[worg]

Hello @singh-harveer one thing I would like is for the maintainer to be currently making use of the library, which is a good way to understand what it does, what's STOMP and maybe have some familiarity with the spec.
Are you using STOMP in any projects? if not, would you be ok to be added as collaborator with Triage access so you can take a look at PRs and depending on how it goes for everyone eventually get Write access?

[singh-harveer]

Hi @worg I have used this library in past but currently not using it. Yeah I am okay with Triage access.

[DaytonG]

I dunno if I'd be a good maintainer, but I could help. Made the "adding stats" MR recently, and use go-stomp in like... I dunno... 10+ services and sidecars? Also been swimming in this code for probably a three years+ at this point. Activemq+STOMP = lots and lots of debugging...