Is this repo maintained?

[MetalRex101]

Last commit was made almost year ago. There are 56 opened issues. Is this repo maintained?

[bygui86]

@proAlexandr can you give any info?

[lnikell]

Hi guys, unfortunately we don't have capacity at this moment to maintain the repository. If someone want to be in charge of this, please let us know.

[paramaggarwal]

I'm interested @lnikell.

[armenr]

@lnikell - Some colleagues and I wouldn't mind taking over maintenance...

[jokesterfr]

Any news on maintenance swap? Or an available alternative?
Some issues need to be fixed.

[DouglasKrouth]

@jokesterfr Interested in this as well; happy to consider opening a fork with a group if there's interest in continuing maintenance as this repo appears to be dead.

[lnikell]

Happy to provide access for any volunteers. If someone wants to take over.

[DouglasKrouth]

@lnikell I'd be happy to help with some of the maintenance work; not sure how much would be required but I should be able to at least help with the open PR's! Goal would be to potentially have a few other people contributing if there's interest, my main goal would be to triage some of the open features and issues right out of the gate :)

Contact info is in my profile, happy to chat if you want over e-mail or anything else.

[DouglasKrouth]

One thing to note is that I'm having an extraordinary amount of build errors on my machine (Ubuntu 22.04 LTS), lot of npm errors that I'm assuming are just from the package being build on/around Node 10.8. Unless I can get those dependency errors resolved, I'm going to have issues supporting the package at the moment :(

[lnikell]

It’s not maintained for quite a while.

[lnikell]

@DouglasKrouth I can give maintainer access for the repo so you can merge pr and do changes if you interested.

[DouglasKrouth]

My apologies @lnikell ; after spending a few hours on this over the weekend, I've been unsuccessful in getting the package to successfully build on any of my machines :( I can continue to poke around with it; however, I don't want to sign onto contributing unless I can get an active dev environment set up

[mrvnklm]

Such a nice and well made application, hopefully someone will contain maintaining.

[hcavarsan]

I used Kube Forwarder a lot, it's an awesome app! but due to some limitations, I ended up not being able to use it anymore.

I managed to set up the application locally and updated some libraries, as well as made some change suggestions in this PR: #107.

However, I soon saw that the project is not being maintained...

But I thank the developers because I know it's hard work to maintain an app like this!

I ended up developing a simple app to manage my kubectl port forward in rust and typescript, My intention is not to compete with Kube Forwarder but to solve some problems and also have a lighter app for these daily tasks.

I am available to help maintain this repository if needed. I can't do it alone due to the daily rush, but I think I can help and bring some learnings I had while developing over the past few months.

[paramaggarwal]

@lnikell kindly share maintainer access with @hcavarsan

[hcavarsan]

Okay, but it's important to mention that I don't have the capacity to maintain this repository on my own. I'm not a good frontend developer, but I'm interested in helping.

I opened a PR updating all the necessary dependencies. In it, I switched from npm to pnpm, updated electron/webpack, and many other things. It's a start and can help those interested in contributing:

#108

[fredleger]

can help if needed. Not a front dev but i can setup great ci/cd and testing envs if that helps in any way

[lnikell]

Happy to share maintainer access to anyone who would love to take control over it.

[hcavarsan]

hi @lnikell , appreciate your openness to granting the community permission to continue evolving Kube-Forwarder., it's really an excellent tool and helps a lot!

i can work on this in my free time, and i think others in this thread can too, and before that, i have a few points to clarify:

what license do u (pixel-point) want to follow? r there any limitations on code or feature changes? will there be any support from pixel-point's side, or would it be independent contributions from our side?

the reason for these questions is that pixel-point is a company, and there's a possibility that we might invest efforts into this and then the code could be closed or something similar.

sorry if my msg seems "aggressive," but my intention is just to help contribute to the app, and i need to know this before accepting the challenge.

anyway, thanks a lot for what u guys have done with kube-forwarder and for making it open source, not many companies do that without profit motives.

[fredleger]

Adding my 2 cents here. I think questions raised by @hcavarsan are legit, and I can join in the same questioning without any bad feelings at all behind it.

Another way to ensure that could be also to consider transferring the project either to @hcavarsan or even better to a foundation like CNCF, Apache etc.... Then the efforts can be put by everybody here with more confidence in the future of this nice project.

This also ensure that the "DEAD REPO" question is less possible to arise because the project got stronger community and visibility.

@lnikell did you already consider such points ?

[fredleger]

up ?

[maxhahn]

I would also really like to see this repo staying alive. It fits a really specific need which is not met as concisely by other tools!