Add go tools section for go-cfclient

[sneal]

This is to start the discussion around moving the go-cfclient from cloudfoundry-community to this Github organization. The go-cfclient is the defacto Golang client library for the CF v3 API and is used by numerous consumers including some that have become critical to the operation of many CF deployments like cf-mgmt

[calebwashburn]

Approve moving this repo to cloudfoundry proper

[stephanme]

I support adding a Go Tools area to the ARI WG. Language clients with working and complete CF API v3 support are important since CF API v2 is deprecated and is known for having performance problems.

[vipinvkmenon]

Kindly Approve this PR. I am looking forward to seeing this officially part of the Cloudfoundry Community

[beyhan]

@stephanme will take care to get this merged.

[stephanme]

@sneal: TOC agreed to transfer the go-cfclient from cloudfoundry-communit org into the cloudfoundry org, as an own area in the ARI WG as you proposed.

The next steps are:

1. Please amend this PR to get an empty go-cfclient repo created. You need to add the go-cfclient repository to the file org/cloudfoundry.yml. You find the necessary change in this repo on branch go-tools (70be47a).
2. I will then merge this PR. The org automation will create an empty go-cfclient repo and assign all necessary teams and access rights.
3. Then I will ask @christopherclark to transfer https://github.com/cloudfoundry-community/go-cfclient to https://github.com/cloudfoundry/go-cfclient, effectively replacing the empty repo created in step 2.

[sneal]

@stephanme I pulled in the required commit to this PR that adds the go-cfclient repo to this org.

[vipinvkmenon]

Hi All the https://github.com/cloudfoundry/go-cfclient seems to be empty. Has the transfer been started?

[beyhan]

Hi @vipinvkmenon,

the https://github.com/cloudfoundry/go-cfclient seems to be empty. Has the transfer been started?

I added this to the topics for the tomorrows TOC meeting. I will provide an update.

[christopherclark]

I have transferred the repository, and automation should soon update permissions.