Add section to our site for people writing brokers

[carolynvs]

We should add a section to the docs homepage with information for people writing brokers

• Best practices about what info we stuff into the context Why do we send namespace.UID ? Consider changing directly to namespace. #2221.
• Pointers to the osb-starter-pack, and the server/client libs.
• Link to osbkit, and minibroker as examples

[jeremyrickard]

Should we limit this to osb-starter-pack and server/client libs? I think for Go these are probably the best. Should we include other languages (i.e. Pivotal has this via Spring https://github.com/spring-cloud/spring-cloud-open-service-broker)

[MHBauer]

#1678

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.