You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2i2c has identified three kinds of groups that we provide managed hubs:
Distributed research hubs
Educational hubs
Single-group research hubs
Reviewing our existing and upcoming hubs here are some communities that could serve as "archetypes" for these different hub models:
Distributed research hub
e.g., Pangeo (as an existing hub)
e.g., Alabama Water Institute (as an upcoming hub)
Education hub
e.g., U Toronto
Single-group research hub
e.g., MEOM SWOT at U Grenoble
I am planning to curate and prepare documentation for these specific hubs that could be reused for all of our hub communites. These particular choice of example hubs is representative of our different kinds of groups and I am open to suggestions if there are communities that would be a better examples (in replacement or addition) to the ones identifed above.
Proposal
No response
Updates and actions
No response
The text was updated successfully, but these errors were encountered:
I think this is a great idea! Having these hub personas well defined is super important not only from the community perspective but also at the time to come up with a complex (and probably composable) billing model suited for each of those ones.
Context
2i2c has identified three kinds of groups that we provide managed hubs:
Reviewing our existing and upcoming hubs here are some communities that could serve as "archetypes" for these different hub models:
I am planning to curate and prepare documentation for these specific hubs that could be reused for all of our hub communites. These particular choice of example hubs is representative of our different kinds of groups and I am open to suggestions if there are communities that would be a better examples (in replacement or addition) to the ones identifed above.
Proposal
No response
Updates and actions
No response
The text was updated successfully, but these errors were encountered: