Skip to content

Commit 483fd94

Browse files
committed
add some text about a workshop hub
1 parent 90ded7b commit 483fd94

File tree

1 file changed

+8
-0
lines changed
  • content/interactive_computing

1 file changed

+8
-0
lines changed

content/interactive_computing/hubs.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,14 @@ Right to Replicate.
1212

1313
## 2i2c Workshop Hub
1414

15+
A workshop hub is used short period, event style workshops where the data needs to persist only for the duration of the workshop event (could be multi-day). As well, the users on a workshop hub are not permanent, ongoing members of the community. Their identities on a workshop hub only need to persist for the duration of the workshop.
16+
17+
The advantage of a workshop hub, is that distinguishes between the home directories of persistent JupyterHub where I, as workshop participant, may have separate projects created before the workshop or completely independent from the workshop. It allows communities representatives to delete data on a workshop hub with additional degree of safety because the contents of the files on a home directory on a workshop hub only have meaning during the workshop or in the immediate days afterwards. A community can reset a workshop hub back to clean state without needing to sort between users who were invited to participate in a workshop style event and users who are long time, on going users of a community hub.
18+
A workshop home is not ephemeral because files may need to persist between separate sessions of a workshop.
19+
20+
A community would periodically request that the data and the accounts on the the workshop hub be removed entirely.
21+
22+
Depending on the community, it may or may not have the same profile or authentication method the community hub. The distinguishing feature is how long the data is intended to persist on the workshop hub.
1523

1624
## 2i2c Binder Hub
1725

0 commit comments

Comments
 (0)