We should add more clear definition for the knative-sandbox about community

[matzew]

To me "gh/knative" is the "core" bits, mainly serving and eventing. Of course, pkg, test infra etc as well

Now, I'd like to see a knative-contrib (or -extensions) org. on GH, that could have:

• the different ingress solutions, bits from eventing-contrib (e.g. kafka, or couchDb)

And finally I'd like to see a knative-incubator (as a better name for "sandbox") where the community can "incubate" on ideas and APIs, with the goal that those repos eventually will graduate to either knative or knative-contrib org (a bit like the Apache Incubator)

[evankanderson]

This is something for Steering to work out, but I think they'd be happy to see references to places where this has worked well in other communities.

[evankanderson]

Related: #131

[evankanderson]

There were questions at the last TOC meeting about the history of Knative-Sandbox, so I drafted a quick doc:

https://docs.google.com/document/d/1vmzL_DZ6oUr7x3hLq09H6tomeRPPccPdverdngFVJM8/edit#

Mostly, it summarizes what's already written at the start of #23 , but adds some additional "threading the needle" of historical context.

[evankanderson]

Paul, can we get this in as an interim step towards nirvana, rather than needing to make things perfect in one go?

[evankanderson]

More specifically, I'm asking about converting What to do with Knative-Sandbox](https://docs.google.com/document/d/1e0PpX4uUaaolF7k5p05ZK_ScjpS5VRiK5y8cCg4oH7Q/edit) to markdown and considering it current policy (which can always be amended further if needed).

[evankanderson]

Please take a look at the suggested text in #149