-
Notifications
You must be signed in to change notification settings - Fork 93
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
Requesting Druid PMC for write permission on repo #329
Comments
@himanshug @fjy @gianm @nishantmonu51 @xvrl |
Unfortunately, the druid-io org on github is a legacy org that the Apache Druid PMC doesn't control. Some PMC members have access as individuals, but the PMC as a whole does not. IMO, it's best to move away from this repository in one of two ways:
If anyone wants to do either one of those, let us know and we can help make it happen. |
This would be the most feasible approach for long term. I will maintain the fork, also calling in for collaborators , this project has great potential for becoming a control plane for running apache druid. |
This is great news, @AdheipSingh. Excited for the future of Druid Operator |
This is really great news. We have been thinking of similar options since the druid operator is an integral part of running druid |
Thanks, @AdheipSingh !! So, going forward, should we fork off from your fork then? Can you provide us with the details once the new fork is set up? |
By end of this week. Yes feel free to fork. It would be great to add in collaborators from your teams. |
I have moved the repo to https://github.com/datainfrahq/druid-operator
|
Thanks @AdheipSingh! Merged your PR #336 as well. |
A humble request to druid PMC to help in maintaining the repo by at least granting write access to merge PR's and cut releases.
@himanshug @fjy @gianm @nishantmonu51 @xvrl
The text was updated successfully, but these errors were encountered: