cloudfoundry-incubator/cf-extensions

CF-extensions hub project

cf-extensions's Issues

CIs into the .cf-extensions.json model

Standardizing the project information through the cf-extensions.json model is a great idea, thanks!

As a maintainer of https://github.com/cloudfoundry-community/cf-docs-contrib/wiki/Design-Documents sidebar which includes concourse pipeline entry points, I would love to see this data collected for extension projects.

multiple GH repos into the .cf-extensions.json model

I see may project team having multiple github repos (e.g. for credhub), supporting a list or a regular expression might help discoverability of these repos by the community.

( Split out of #2 )

Add .cf-extensions to your repo to be listed in cloudfoundry-incubator.cf-extensions

Add .cf-extensions file to your repo so that it shows correctly in the CF-Extensions catalog.

{
  "description": "ADD DESCRIPTION HERE",
  "tracker_url": "",
  "proposal_url": "https://docs.google.com/document/d/1cpyBmds7WYNLKO1qkjhCdS8bNSJjWH5MqTE-h1UCQkQ/edit?usp=sharing",
  "logo_url": "https://github.com/cloudfoundry-incubator/cf-extensions/blob/master/docs/images/cf-extensions-proposal-logo.png",
  "icon_url": "https://github.com/cloudfoundry-incubator/cf-extensions/blob/master/docs/images/cf-extensions-proposal-icon.png",
  "owner_company": "ADD OWNER COMPANY HERE",
  "contact_email": "[email protected]",
  "proposed_date": "2017-08-14 14:12:30.274897815 -0700 PDT"
}

This is a JSON formatted file. The default values in the file are for you to get started. You should edit to match your project's data.

For example, the field tracker_url should contain your project's tracker URL, and so on.