Call for maintainers

[mrtazz]

The progress on this project has been more than slow over the last couple of years. And I always thought I'd be able to get back to it. Since creating the initial library for my Master thesis 10 years ago, I have in all honesty not had a lot of use for it. And have mostly maintained it because others seem to have found it useful.

However I am finding myself with less and less time to devote to this project. So if anyone is interested in taking up maintainership and become a collaborator on the repo, please chime in on this issue. Ideally you already have some contributions in the project. If not you can start now and help out with triaging issues and opening pull requests for bugs or features.

[ElonDusk26]

ive already created a fix for #158 and would like to contribute more (and share my patch) but in all honesty i have no idea how to use github. I must say im impressed of your work! Good Job creating this library

[KaiPetzke]

I am basically in the same position as ElonDusk26... So, to look over one or two submissions in a month would be ok for me, but actual development on this library is currently not possible for me.

[rfm-bot]

🚧 Is this repo looking for support?
Hello, we created this issue becuase the user @sospedra told us you are calling for maintainers.
✅ If you're looking for collaborators no action is required.
👮🏻‍♂️ If this repo is well-supported please put a comment here sospedra/rfm#73 and we'll close it immediately.
Sorry for any inconvinience. We understand this message can feel spammy but we really think is good to double-check first with the current owners :)

[KaiPetzke]

So how do we continue from here? Could I or ElonDusk take over as maintainer? What is required to do so?

[edwinpjacques]

HI @mrtazz I have created a MR #160 to fix CI and allow support for GET that maintains an open connection (useful for implementing Kubernetes "watch" API). I wouldn't mind sharing the load to maintain the project. Please ping me.

[mrtazz]

Sorry this took so long. @edwinpjacques I invited you to the repo.

As for @ElonDusk26 and @KaiPetzke, since you both mentioned you have limited time and experience with GitHub, I think a good way to start contributing and helping the project out for now is triaging issues and pull requests. And work with @edwinpjacques to get things closed and merged.

Thanks all for taking an interest in keeping the project going!