does this structure make sense?

[neuromusic]

should this repo contain the tutorial, examples, and workshops?

or should we create one repo for each of those?

@nicain @saskiad

[nicain]

What is the motivation for moving them out of the SDK?

[neuromusic]

• Gallery notebooks may have dependencies that are beyond what we want to maintain in AllenSDK
• We don't want to add EVERY technical workshop to the AllenSDK
• This only moves the "tutorial" out of the AllenSDK. More specifically, it forks it.
• This repo is the responsibility of the BSP team to maintain, with AllenSDK as a dependency (no need to wait for version bump of AllenSDK) to distribute.
• This is a repo of example notebooks and that's it. Analogous to SWDB_2018, etc.
• This is amenable to building a binder of examples.
• If we decide we want these built into the AllenSDK docs (e.g. through sphinx-gallery), that's a decision that can be made AFTER we have a robust repo of useful examples.

The primary workflow for a user is...

1. pip install allensdk
2. Clone this repo
3. jupyter notebook