-
Notifications
You must be signed in to change notification settings - Fork 859
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fork Kafdrop due to inactivity? #321
Comments
@davideicardi please count me in |
Yeah, why not? It's too useful to let it die a maintenance death... |
Yes, That'll be really great! And please review PR #282 to your fork |
You can count me in |
I have been contacted by @ekoutanov, and fortunately he says that kafdrop is still active!! So no need to fork, that is always a good thing.🥳 But we still need your help, so please stay tuned for further news! I will close the Kafdrop organization. |
Heya folks, Firstly, thanks everyone who's put their hand up for contributing to the project, and all those who're thinking of doing so. Unfortunately, I haven't been able to commit any time over the last year to do any work on it. @davideicardi and I have indeed had a few email exchanges to determine what the best way forward is. The consensus for now is to maintain the present GitHub repo, which is heavily SEO-optimised, and to add people as maintainers. All the best! |
Hello everybody!
Current maintainer of Kafdrop is not more active on the project. (@ekoutanov please correct me if I'm wrong :-) )
So I'm thinking to create a fork inside a new kafdrop organization.
But I need some help. Is someone interested in joining the organization?
If I found at least 2/3 developers I think we can try to continue the work in our spare time.
The text was updated successfully, but these errors were encountered: