Skip to content

ARI: merge OSB API area into CAPI #1172

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

Merged
merged 1 commit into from
Jun 3, 2025
Merged

ARI: merge OSB API area into CAPI #1172

merged 1 commit into from
Jun 3, 2025

Conversation

stephanme
Copy link
Member

- OSB API area got orphaned when the last approver was removed by #1162 (inactive user cleanup)
- decision in ARI WG meeting on 25-05-27 to add the repos to the CAPI area
@stephanme stephanme marked this pull request as ready for review May 28, 2025 06:11
@stephanme
Copy link
Member Author

In the end, this is just documentation as the repos are not located in cloudfoundry github org. Once merged, the access rights in github org openservicebrokerapi should be consolidated.

We should consider moving the repos into the cloudfoundry org to benefit from the org automation. rfc-0036-multiple-github-orgs.md requires that a WG contains only repos from one CFF github org.
On the other hand, https://www.openservicebrokerapi.org/ aims to define a platform independent service integration which may justify an own github org.

@stephanme stephanme requested a review from Gerg May 28, 2025 06:40
stephanme added a commit that referenced this pull request May 28, 2025
- contains 2 repos that are assigned to ARI WG, see also #1172
- conflicts with rfc-0036-multiple-github-orgs.md - a WG must only contains repos of one github org
@stephanme stephanme merged commit afee32c into main Jun 3, 2025
2 checks passed
@github-project-automation github-project-automation bot moved this from Inbox to Done in CF Community Jun 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants