Skip to content
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

Allow Operator to Be Namespace-Scoped #579

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

rurkss
Copy link

@rurkss rurkss commented Mar 27, 2023

the point of this PR is to make redis-operator work inside of a namespace

@rurkss rurkss requested a review from a team as a code owner March 27, 2023 20:27
@rurkss rurkss closed this Apr 7, 2023
@rurkss rurkss reopened this Apr 7, 2023
@rurkss rurkss changed the title redis operator under its namespace Allow Operator to Be Namespace-Scoped Apr 7, 2023
@benlangfeld
Copy link

Hi @ese ! Firstly, thank you to Spotahome for open-sourcing this project and to those who maintain and contribute to it. We’ve adopted it at my company and it has been very useful.

There are, however, several points where we have had to make modifications. This PR is one of them, but absent any feedback here or on several other open PRs from other contributors we have become demotivated to submit them all upstream. We’re now at the point where we need to decide if we’re going to put effort into getting all of our modifications integrated upstream or formalise our fork.

In order to help us make this decision, I’m interested in understanding more about the governance of this project and what contributors should plan for in terms of reviews and merges. Do the maintainers have time available to review unsolicited contributions or is the intent for the project to be more of a publication? Is there some mode of collaboration that you would like for contributors to follow to facilitate integrating proposed changes?

Thanks for your work on this project and for your attention here, it’s most appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants