Enhance Booster Contribution Experience

ALRubinger commented 7 years ago

As we have begun to socialize Launch throughout RHT, this request has been thematic. Groups involve include BobMcW, Open Innovation Labs, RHOADS, OSIO teams thus far.

Needs to be as encouraging as possible to contributors. Look at:

A Contribution Guide explaining how to contribute a Booster
How to surface Boosters which are not part of the standard Missions structure (or even the Catalog!)
How to allow Boosters to be independently upgraded in Launch without revving the Booster catalog release (we currently have this by nature of the master/next branches, but we've been requested to let the environments control their own). Sync with Strachan particularly on this.

ALRubinger commented 7 years ago

On the point of splitting up the catalog to be owned by the platforms using Launch, see notes in https://github.com/openshiftio/appdev-planning/issues/47

ALRubinger commented 6 years ago

Should be a part of, or linked from launcher.fabric8.io: #86

wtrocki commented 5 years ago

Idea

I'm coming from a community that will look for creating boosters. Github allows now to create topics like #nodejs etc. Do you think it will be possible to use something like #rh-launcher-booster as tag for repositories for tracking community boosters/booster catalogs?

fabric8-launcher / launcher-application

Enhance Booster Contribution Experience #882

Idea