Rename Elafros to Knative

[dewitt]

The Elafros placeholder name has served its purpose well, but it is time to retire it in favor of something we can build a long-term brand around. Thanks to an extensive search, where we worked hard to evoke the spirit of Kubernetes native software, we're happy to have landed on Knative (pronounced /ˈnā-tiv/ as in "knowledge" in English, or /'kna-tiv/ as in "Knie" if German or Dutch is more natural for you.)

Process-wise we have a few steps to follow, and let's use this issue as the umbrella bug to track them. This can happen before or after the renaming of the elafros/elafros repository to elafros/serving (see issue #760). We have the github.com/knative repository reserved and can free that up when we're ready to make the change.

During this move we will also want to create a top-level pinned 'community' repository to hold all org-wide documentation, such as governance guidelines and whatnot. I will create a follow up issue for that.

The end result after this move should look like:

knative/build
knative/build-templates
knative/community
knative/eventing
knative/install
knative/serving

Note that we've done a fairly thorough review of many naming options and have discussed it privately with many of you and are confident that this will stick, but if there are any strong objections, please share them here. Preferential objections are of course also fair game, but it would be quite a high bar to start over at this point, as naming is hard and many otherwise good sounding choices are unavailable for one reason or another.

[mchmarny]

As a non-English speaker, I find Knative exponentially easier to pronounce... so yey!

[mchmarny]

org renamed

[mchmarny]

elafros/elafros renamed to knative/serving

[mattmoor]

This is done with the exception of community, which is tracked separately.