is any maintainer alive in this project ?

[prune998]

I can help if needed....

[prune998]

@hidetatz I've been trying to call you out every possible ways I found and never got any answer.

I'm a speaker at the next KubeCon US 2022 in Detroit and I wanted to present kubecolor as part of my talk, but the lack of activity in this project is refraining me.

I'd really like to hear from you soon.
If you're not willing to spend time on this project, can you add me as a maintainer ? I'm sure there are other people willing to help here too.

If I don't hear back from you soon, I will fork the project and start maintaining and promoting it so the community can have a working solution for the long term. That said, I would rather be a maintainer here and keep this project active.

Please take few seconds to reply to your users :)

[anthr76]

+1 this project is widely used by myself and would love to see it's development continued without a fork.

[prune998]

OK all I just forked it to https://github.com/kubecolor/kubecolor

I'm going to review and port all the current opened PRs if they make sense. Please if you read this, create new PRs on https://github.com/kubecolor/kubecolor

If you want to join and help as a maintainer please also ping me.

[fkoner]

@prune998 Thanks for the initiative!
I think also the formula needs to be cloned:
https://github.com/hidetatz/homebrew-tap

Would you mind to fix these ones?
#90
hidetatz/homebrew-tap#5

[prune998]

I will have a look ! thanks for the heads-up

[prune998]

This is fixed.
Get it at https://github.com/kubecolor/kubecolor or brew install kubecolor/tap/kubecolor

[Yoshyn]

@prune998 : Hi, thanks for your work :)

However, it can be a little confusing in the current state

After installing a new laptop I found it impossible to install kubecolor.
So I look at the issues (example this one : #109) and I find your repo and at first glance feel insecure.

After, I find this issue and look most on the commit made on https://github.com/kubecolor/kubecolor.
You should really indicate in the README of kubecolor this issue and the reason of the fork.

[hidetatz]

Yes I'm alive

[prune998]

Hey @hidetatz !
As you can see I cloned this project to https://github.com/kubecolor/kubecolor

What do you think about it ?
Are you interested to take back the ownership ?

Would you be willing to archive this project in favour of the other one ?

I don't want to hijack your work. Just wanting to provide support, clarity and continuity to this (your) awesome project.

Thanks and happy new year !

[vorburger]

The current situation between these 2 projects seems confusing to users; it would be great if this were clarified between @hidetatz and @prune998 ...

[prune998]

@vorburger and I'm really opened about it but I can't make that happen by myself :)

[hidetatz]

@prune998

At least now, I will not throw this project's ownership away. I will keep maintaining this project, but it will happen only when I have time (this is the same as the other OSS projects).

However, I do not have strong opinion about https://github.com/kubecolor/kubecolor. While I think duplicated projects are confusing to users, I actually cannot stop being forked the hidetatz/kubecolor while I keep the current kubecolor LICENSE (this is also the same as the other OSS). If community forks the project and make it better, naturally the users will switch to kubecolor/kubecolor, I think it's fine.

I guess we have 3 options:

• Archive hidetatz/kubecolor and transfer the project to kubecolor/kubecolor
  • I will unlikely choose this because I currently do not have any reasons to archive hidetatz/kubecolor.
• Archive kubecolor/kubecolor for clarity.
  • One think we should consider is if I should invite some developers to hidetatz/kubecolor's committer.
• Keep maintaining both.
  • I think this is also ok.

[prune998]

I like the first option, as I feel kubecolor/kubecolor is better than having the creator/maintainer name in it. The reason you have to go this way is to provide clarity to users by picking only one of the two.

Option 2 could be a possibility, but considering option 1, then it would be the other way around and archive hidetatz/kubecolor

I don't like option 3 at all, at it's less clear for users and we'll always have questions, issue and out of sync problems.
Actually, I don't want to maintain kubecolor if there is some else actively maintaining it. I just did it because the project was dead for a year and a half. As you, I don't have much time and I don't want to duplicate the efforts.

My option 4 would be to archive hidetatz/kubecolor and I give you back the full ownership of kubecolor/kubecolor. And then if you feel you want help to maintain it, you can still add me back as a maintainer.

I guess the only diff in the code right now is related to the color schema change. While I understand your point of view that color scheme is a personal choice, I see an opportunity to add a sort of color templates where each users could decide on the color scheme they want (or need... color deficiency is actually a big thing).

Do you think I could make you change your mind on keeping kubecolor/kubecolor ?