Streamline chef creation process

[kollivier]

Currently, creating a new chef requires a series of manual steps, which include the following:

1. Creating a github repo
2. Checking out the github repo locally
3. Using cookiecutter to apply the chef template.
4. Committing the github repo
5. Adding the chef to sushibar
6. Creating the new sushibar entry, then retrieving the channel id
7. Adding the channel id, github repo, and other information to the tech specs
8. Linking the sushibar entry to the tech specs, the git repo, and the trello card
9. Using fab commands to checkout the repo on vader

Jumping between docs and copying and pasting information causes this process to take much longer than it should, and creates a lot of steps to remember. I think most of these steps could be automated using fab commands, and it would save a lot of time in new chef creation.

Also, this process creates several "sources of truth" for the state of the chef - the trello card, the tech specs doc, and the sushibar. Only the Trello card provides notifications currently (Docs does but only for comments it seems?).

[ivanistheone]

Agree with need for more automation. Looking forward to discuss with you when I get back.

Some comments below:

Using cookiecutter to apply the chef template.

This could be automated and improved so it is more useful --- give me a e.g. start with a youtube-channel-sample-code chef.

Adding the chef to sushibar

That's not a necessary step. The sushibar registration will happen automatically on first run. The idea for this feature was to help out new chef authors who are just getting started by providing links to important docs (a bit like onboarding docs for contractors).

Adding the channel id, github repo, and other information to the tech specs

That's more of a pre-work step, when handing over to a contractors since not everyone can create repos on github. This is also a good time for @sushops to "double check" the channel name + source_id + language name conventions are adhered to.