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

Remove receptor from ecosystem #210

Merged
merged 1 commit into from
Dec 14, 2023

Conversation

oraNod
Copy link
Collaborator

@oraNod oraNod commented Dec 14, 2023

issue #208

@oraNod oraNod merged commit 017b0a6 into ansible:main Dec 14, 2023
1 check passed
@samccann
Copy link
Collaborator

fwiw I'm still not convinced removing it is the right thing to do here. As was mentioned on a previous related Pr - if it's in the ecosystem it's in the ecosystem. I disagree with us acting as gateways for what project is 'good enuf' to be on this page. Perhaps in a future iteration, we have this main ecosystem page, and then an 'incubator' page or something. Something to discuss in the new year as we tackle governance etc and can have guidelines on what belongs here on this page.

@Andersson007
Copy link
Contributor

@samccann i believe we're not gating here. This case is rather exceptional as there's no value for outside users/contributors in seeing the project whatsoever.
It's used somewhere in AAP deep under the hood and, i think, the only reason it lives under the ansible org is that it must do so because of the legal requirements for OSS.

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.

3 participants