Move template registry to its own repository about helm HOT 5 CLOSED

Initial thinking:

• Title is Kubernetes Template Registry
• Repository name is templates
• Directory structure is category based (i.e., categories at top level, sub categories below them, etc.)
• Initial categories include common and storage.
  • replicatedservice lives in common
  • redis lives in storage

from helm.

Plans may be changing here, so we should not pull the trigger on this just yet.

from helm.

Assigned this to @vaikas-google, since he's already signed up to create the top level repository.

from helm.

Assigning this task back to me.

from helm.

Preparing to implement this issue.

The implementation will follow the process for moving a folder described at Detach subdirectory into separate Git repository and the conventions for organizing a repository described in #25.

Files in the current location (https://github.com/kubernetes/deployment-manager/tree/master/templates) will move to the new location (https://github.com/kubernetes/application-dm-templates) as follows:

• README.md at the top level of the current location will move to the top level of the new location.
• The contents of nfs, redis and spark at the top level of the current location will move to a folder named storage in the new location.
• The contents of replicatedservice in the current location will move to a folder named common in the new location.
• README.md will be updated to describe the organization of the new repository.
• The template registry documentation will be updated to capture the decisions recorded in #25.
• References to the relocated templates in other relocated templates and in kubernetes/deployment-manager/examples will be updated to reflect the change.

/cc @vaikas-google, @bmelville, @zmerlynn

from helm.