Replies: 1 comment 3 replies
-
There was a bit of an effort to create these formally at the start but it didn't get very far and was superceded by the User Roles documentation. Here's as far as we got: https://docs.google.com/document/d/17uqJ61lcVErfFm7uzWqMMopbLLAO6GSSR46KlV5zJ24/edit |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
(N.B. this is very much a duplicate of hubverse-org/hubUtils#11)
One of the things that strikes me as I walk through the documentation is that people interact with the hubs in very different ways depending on their role. Having a clear description of what these roles entail would be really helpful to structure the documentation in a way that meets the needs of the people who assume these roles so that (e.g.) a modeller does not have to sift through hub admin documentation to understand how to format their output.
From my initial discussion with @bsweger, she identified four roles for a hub:
There may be more, but this is what I'm starting with. I would like to gather some user personas for these roles. Please help me by sharing what you know about these roles.
Importantly, user personas are not just what the roles are doing, but also what the people in these roles want to accomplish. Perhaps most importantly, they include factors outside of the role responsibilities that may influence how much time or energy someone may have to spend on their role.
As an example of user personas, at my previous work, we worked for a community of volunteers who were teaching researchers to work with code and data. These are the personas for learners in our workshops: https://carpentries.org/audience/
Beta Was this translation helpful? Give feedback.
All reactions