Opening this issue as a follow on to discussion in kubeflow/community#454 and at the community meeting.

Notebooks code is currently in kubeflow/kubeflow
https://github.com/kubeflow/kubeflow/tree/master/components/jupyter-web-app

kubeflow/kubeflow has historically been a catchall and historically as projects have matured they have moved out of kubeflow/kubeflow into project specific repositories.

Now that we have formed working groups we would like working groups to take responsibility for managing their repositories to deal with kubeflow/testing#737.

So going forward rather than creating new repositories in Kubeflow when WGs need a new repo we would like them to create this repo in a GitHub org they own/administer so they can bear responsibility for administering the repo and managing access control.

@kubeflow/wg-notebook-leads WDYT? It looks like you already have a GitHub org https://github.com/kubeflow-kale which is where Kale lives. So what's blocking from creating repos there for notebook controller/notebook images etc...?

Can we rename the GitHub org? I think "Kubeflow " naming is boring. Given the aspirations of the WG regarding the datascientist experience; "kubeflow-kale" and "kubeflow-notebooks" seem a bit limiting.