Add initial structure to the repository

[calebamiles]

One of the primary purposes of this SIG repository is to add more structure than previously existed in the kubernetes/community repo. I propose the following directory structure for the repo

├── LICENSE
├── members.md
├── README.md
├── release-process-documentation
│   ├── documentation-guides
│   │   ├── update-release-docs.md
│   │   └── updating-docs-for-feature-changes.md
│   └── github-guides
├── releases
│   ├── release-1.2
│   ├── release-1.3
│   ├── release-1.4
│   ├── release-1.5
│   ├── release-1.6
│   └── release-1.7
├── security-release-process-documentation
│   └── security-release-process.md
└── ephemera
    ├── cherry-picks.md
    ├── issues.md
    ├── patch-release-manager.md
    ├── README.md
    ├── scalability-validation.md
    └── testing.md

where

• release-process-documentation stores process docs for the release team and the community
• releases contains historical information about previous releases such as the team list and the release notes draft
• security-release-process-documentation provides quick access to information about our security release process
• ephemera is a staging directory which should be generally empty

[jdumars]

LGTM