differences for PR #244

index.md

@@ -48,6 +48,24 @@ If you are looking for a lesson on using Singularity containers (instead of Dock
 - The lessons will sometimes request that you use a text editor to create or edit files in particular directories. It is assumed that you either have an editor that you know how to use that runs within the working directory of your shell window (e.g. `nano`), or that if you use a graphical editor, that you can use it to read and write files into the working directory of your shell.
 
 
+::::::::::::::::::::::::::::::::::::::::::::::::::
+
+:::::::::::::::::::::::::::::::::::::::::  callout
+
+## Target audience
+
+This lesson on the use of Docker is intended to be relevant to a wide range of
+researchers, as well as existing and prospective technical professionals. It is
+intended as a beginner level course that is suitable for people who have no
+experience of containers.
+
+We are aiming to help people who want to develop their knowledge of container
+tooling to help improve reproducibility and support their research work, or
+that of individuals or teams they are working with.
+
+We provide more detail on specific roles that might benefit from this course on
+the [Learner Profiles](/profiles.html) page.
+
 ::::::::::::::::::::::::::::::::::::::::::::::::::
 
 :::::::::::::::::::::::::::::::::::::::::  callout

learner-profiles.md

@@ -1,5 +1,99 @@
 ---
-title: FIXME
+title: Learner profiles
 ---
 
-This is a placeholder file. Please add content here. 
+Here we provide some example profiles of people who represent the target
+audience for this lesson. These example scenarios are designed to give you an
+idea of the different reasons people might want to learn Docker and the types
+of roles that they might hold.
+
+The profiles provided here and the individuals described are fictional but they
+represent the lesson developers' experiences of teaching members of the
+research community about Docker and other container technologies over a period
+of several years. They also incorporate feedback from instructors involved in
+pilot runs of this course.
+
+Note that containers are applicable across a wide range of use cases within the
+research and High Performance Computing communities. These profiles are not
+intended to cover all areas but rather to offer some examples of the types of
+roles people learning this material might hold and their reasons for learning
+about containers.
+
+## Individual learner profiles
+
+***Nelson is a graduate student in microbiology.*** They have experience in running Unix shell
+commands and using libraries in R for the bioinformatics workflows they have developed.
+They are expanding their analysis to run on 3000 genomes in 200 samples and they have
+started to use the local cluster to run their workflows. The local research computing
+facilitator has advised them that Docker could be useful for running their workflows on
+the cluster. They'd like to make use of existing containers that other bioinformaticians
+have made so they want to learn how to use Docker. They would also be interested in
+creating their own Docker images for other lab members and collaborators to re-use their
+workflows.
+
+***Caitlin is a second year undergraduate in computer science examining Docker for the first
+time.*** She has heard about Docker but does not really know what it achieves or why it is
+useful. She is reasonably confident in using the Unix shell, having used it briefly in
+her first year modules. She is keen to find jump-off points to learn more about technical
+details and alternative technologies that are also popular, having heard that container
+technologies are widely used within industry.
+
+***Xu, a materials science researcher, wants to package her software for release with
+a paper to help ensure reproducibility.*** She has written some code that makes use of a
+series of Python libraries to undertake analysis of a compound. She wants to (or is
+required to) make her software available as part of the paper submission. She
+understands why Docker is important in helping to ensure reproducibility but not the
+process and low-level detail of preparing a container and archiving it to obtain a DOI
+for inclusion with the paper submission.
+
+***Bronwyn is a PhD student running Python/R scripts on her local laptop/workstation.***
+She is having difficulty getting all the tools she needs to work because of conflicting
+dependencies and little experience with package managers. She is also keen to reduce
+the overhead of managing software so she can get on with her thesis research. She has
+heard that Docker might be able to help out but is not confident to start exploring
+this on her own and does not have access to any expertise in this within her local
+research group. She currently wants to know how to use preexisting Docker containers
+but may need to create her own containers in the future.
+
+***Virat is a grad student who is running an obscure bioinformatics tool (from a GitHub
+repo) that depends on a number of other tools that need to be pre-installed .*** He wants to be able to
+run on multiple resources and have his undergrad assistant use the same tools. Virat
+has command line experience and has struggled his way through complex installations
+but he has no formal CS background - he only knows to use containers because a departmental
+IT person suggested it. He is usually working from a Windows computer. He needs to
+understand how to create his own container, use it locally, and train his student
+to use it as well.
+
+## Group profiles
+
+In addition to our individual learner profiles above, we also look at three
+more general groups who may want to learn about containers. This is intended to
+help you get a perspective of the different types of skills and expertise that
+learners engaging with this material may have:
+
+- **Researchers:** For researchers, even those based in non-computational domains, software
+  is an increasingly important element of their day-to-day work. Whether they are writing
+  code or installing, configuring and/or running software to support their research, they
+  will eventually need to deal with the complexities of running software on different
+  platforms, handling complex software dependencies and potentially submitting their code and data to
+  repositories to support the reproduction of research outputs by other researchers, or to
+  meet the requirements of publishers or funders. Software container technologies are valuable
+  to help researchers address these challenges.
+
+- **RSEs:** RSEs -- Research Software Engineers -- provide software development, training
+  and technical guidance to support the development of reliable, maintainable, sustainable
+  research software. They will generally have extensive technical skills but they may not
+  have experience of working with or managing software containers. In addition to working with
+  researchers to help build and package software, they are likely to be interested in how
+  containers can help to support best practices for the development of research software
+  and aspects such as software deployment.
+
+- **Systems professionals:** Systems professionals represent the more technical end of
+  our spectrum of learners. They may be based within a central IT services environment
+  within a research institution or within individual departments or research groups.
+  Their work is likely to encompass supporting researchers with effective use of
+  infrastructure and they are likely to need to know about managing and orchestrating
+  multiple containers in more complex environments. For example, they may need to provide
+  database servers, web application servers and other services that can be deployed
+  in containerized environments to support more straightforward management, maintenance
+  and upgradeability.

md5sum.txt

@@ -4,7 +4,7 @@
 "LICENSE.md" "b24ebbb41b14ca25cf6b8216dda83e5f" "site/built/LICENSE.md" "2024-06-27"
 "aio.md" "bbb0f59db3ef6dccf60fb4a7a86d3020" "site/built/aio.md" "2024-06-27"
 "config.yaml" "54be1fabc599404a592c83552a49916f" "site/built/config.yaml" "2024-07-26"
-"index.md" "a0429c3e89b940ea353978606add384b" "site/built/index.md" "2024-06-27"
+"index.md" "16a0cc69e6e31090b65bec6484cdf513" "site/built/index.md" "2024-08-05"
 "episodes/introduction.md" "fbd6c719d897bfa342d976928b942d56" "site/built/introduction.md" "2024-08-01"
 "episodes/meet-docker.md" "36a6daa2e4727a8ce88db8a4a1a0fa88" "site/built/meet-docker.md" "2024-08-01"
 "episodes/running-containers.md" "4bd40434e9fee516256b848e2a423f5a" "site/built/running-containers.md" "2024-06-27"
@@ -23,4 +23,4 @@
 "learners/discuss.md" "2758e2e5abd231d82d25c6453d8abbc6" "site/built/discuss.md" "2024-06-27"
 "learners/reference.md" "bbb68ff9187bcebed81d18156df503cc" "site/built/reference.md" "2024-08-01"
 "learners/setup.md" "fd74bc2dd9538bf486391304cb6f6f7f" "site/built/setup.md" "2024-06-27"
-"profiles/learner-profiles.md" "60b93493cf1da06dfd63255d73854461" "site/built/learner-profiles.md" "2024-06-27"
+"profiles/learner-profiles.md" "6fcb80ab2baf4f2762193ae4a6f1294a" "site/built/learner-profiles.md" "2024-08-05"