Skip to content
This repository has been archived by the owner on Jan 21, 2022. It is now read-only.

Moving SB API Swagger definition to OSBAPI repo? #6

Open
avade opened this issue Mar 21, 2017 · 4 comments
Open

Moving SB API Swagger definition to OSBAPI repo? #6

avade opened this issue Mar 21, 2017 · 4 comments
Assignees

Comments

@avade
Copy link
Contributor

avade commented Mar 21, 2017

How would y'all feel about the OSBAPI [1] community owning the swagger definition for the Service Broker API? This would allow it to be easily kept up to date with the latest spec changes.

The proposal would be to move this definition to the OSBAPI repo. We discussed on our working group call today and the consensus amongst those on the call was this would be a good addition to the project.

Before we share this idea with the wider OSBAPI group, I thought I would check to see if this is of interest.

cc @maximilien @duglin

[1] https://github.com/openservicebrokerapi/servicebroker

@avade avade changed the title SB API Swagger definition moving to OSBAPI repo Moving SB API Swagger definition to OSBAPI repo? Mar 22, 2017
@maximilien maximilien self-assigned this Apr 3, 2017
@maximilien
Copy link
Collaborator

I like this idea a lot. Do you mind just submitting a PR to this repo that I will merge that replaces the JSON/YAML with a README.md file that includes a short text describing the move and at least a link to new location?

Thanks,

Max

/cc @midoblgsm

@maximilien
Copy link
Collaborator

Adding @fehguy @davidfetter to discussion, in case they have differing opinions or suggestions.

@fehguy
Copy link

fehguy commented Apr 3, 2017

We could provide an OSS license for the CF team to host the definition in SwaggerHub, and the definition updates could be pushed to the repo of your choice.

https://app.swaggerhub.com/api/cf-demos/cf-broker/2.11

@davidfetter
Copy link

davidfetter commented Apr 4, 2017

A permissive license like MIT or 2-clause BSD would go a long way toward adoption in places where Legal™ is a factor.

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

No branches or pull requests

4 participants