Skip to content

Commit a8f8724

Browse files
Release v1.6.0
1 parent 1316cb8 commit a8f8724

23 files changed

+112
-96
lines changed

.github/workflows/pages-build-deployment.yml

+1-1
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ jobs:
2525
uses: actions/checkout@v3
2626

2727
- name: "Setup Python"
28-
uses: actions/setup-python@v2
28+
uses: actions/setup-python@v3
2929
with:
3030
python-version: 3.x
3131

.gitignore

+1-1
Original file line numberDiff line numberDiff line change
@@ -121,7 +121,7 @@ celerybeat.pid
121121

122122
# Environments
123123
.env
124-
.venv
124+
.venv*
125125
env/
126126
venv/
127127
ENV/

CODE_OF_CONDUCT.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ representative at an online or offline event.
6868

6969
Instances of abusive, harassing, or otherwise unacceptable behaviour may be
7070
reported to the community leaders responsible for enforcement at
71-
datascience@nhs.net.
71+
[england.rapchampions@nhs.net](mailto:england.rapchampions@nhs.net).
7272
All complaints will be reviewed and investigated and will result in a response that
7373
is deemed necessary and appropriate to the circumstances. The project team is
7474
obligated to maintain confidentiality with regard to the reporter of an incident.

README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66
[![licence: OGL3](https://img.shields.io/badge/Licence-OGL3-darkgrey "licence: Open Government Licence 3")](https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/)
77

88

9-
> **This material is maintained by the [NHS Digital Data Science team](mailto:datascience@nhs.net)**.
9+
> **This material is maintained by the [NHS RAP Community of Practice](mailto:england.rapchampions@nhs.net)**.
1010
>
1111
> See our other work here: [NHS Digital Analytical Services](https://github.com/NHSDigital/data-analytics-services).
1212

docs/about.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ hide:
55

66
# RAP Community of Practice
77

8-
> **This material is maintained by the [NHS England Data Science team](mailto:datascience@nhs.net)**.
8+
> **This material is maintained by the [NHS England RAP Community of Practice](mailto:england.rapchampions@nhs.net)**.
99
1010
> You can see some examples of our work [here](https://github.com/NHSDigital/data-analytics-services), including [underlying code to NHS Digital publications](https://github.com/NHSDigital/data-analytics-services#rap-publication-repositories) which have been published as a direct outcome of the service our team provides.
1111
@@ -49,7 +49,7 @@ We have also developed some training resources on:
4949

5050
These resources are intended to help people get started with RAP. We welcome all feedback.
5151

52-
If you think of something worth including, improving, or want to contribute, please [raise an issue on GitHub](https://github.com/NHSDigital/rap-community-of-practice/issues) or contact the team via the NHS England "RAP Community of Practice" MS Teams (internal to NHS England), or [email](mailto:datascience@nhs.net).
52+
If you think of something worth including, improving, or want to contribute, please [raise an issue on GitHub](https://github.com/NHSDigital/rap-community-of-practice/issues) or contact the team via the NHS England "RAP Community of Practice" MS Teams (internal to NHS England), or [email](mailto:england.rapchampions@nhs.net).
5353

5454
You can also follow our guidance on [how to contribute](https://github.com/NHSDigital/rap-community-of-practice/blob/main/CONTRIBUTE.md).
5555

File renamed without changes.
File renamed without changes.

docs/introduction_to_RAP/why_RAP_is_important.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ This community of practice aims to support teams in adopting RAP practices throu
3333
1. **Developing learning materials including reusable templates:**
3434
Most of the learning materials were initially adapted for the NHS England analytical environment, but most are applicable elsewhere.
3535
2. **Offering support as teams establish new working practices:**
36-
We offer in-person support to NHS England teams in the form of bespoke coaching sessions. We also co-ordinate informal weekly drop-in sessions (internal to NHS England) and host monthly workshops, where you can learn from others at different stages of RAP adoption, and get advice. If you would like to attend these please [contact us](mailto:datascience@nhs.net).
36+
We offer in-person support to NHS England teams in the form of bespoke coaching sessions. We also co-ordinate informal weekly drop-in sessions (internal to NHS England) and host monthly workshops, where you can learn from others at different stages of RAP adoption, and get advice. If you would like to attend these please [contact us](mailto:england.rapchampions@nhs.net).
3737

3838
This work is prompted by the observations that teams can struggle to adopt RAP practices without support. While no one element of RAP is particularly difficult, learning several new skills at the same time as delivering BAU is challenging. Teams can struggle to protect time to embed these practices. (The Statistics Authority report on [the barriers to RAP adoption](https://osr.statisticsauthority.gov.uk/publication/reproducible-analytical-pipelines-overcoming-barriers-to-adoption/) is an excellent discussion of the challenges in rolling out RAP).
3939

.github/workflows/RAP-Release-Workflow.md docs/our_RAP_service/rap-release-workflow.md

+59-47
Large diffs are not rendered by default.

docs/our_RAP_service/typical-engagement-flow.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ Nevertheless, the text below lays out the type of activities that occur in acros
1313

1414
- Hear about RAP through show-and-tells, internal advertising, slack, etc.
1515
- Have a look over the [RAP Community of Practice][3] pages to get a sense of what it is all about.
16-
- Reach out to the [RAP team](mailto:datascience@nhs.net) for a chat
16+
- Reach out to the [RAP Community of Practice](mailto:england.rapchampions@nhs.net) for a chat
1717
- Together with someone from the RAP team, walk through the [levels of RAP][4] page and consider the team's scale of ambition.
1818
- If you are keen to proceed, pass the request to the RAP product owner for prioritisation and resourcing
1919
- Get a start date in the calendar. Think about publication timing, team capacity, etc. to choose a good time.

mkdocs.yml

+1
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,7 @@ nav:
3131
- RAP pre-engagement Questionnaire: our_RAP_service/rap-pre-engagement-questionnaire.md
3232
- Programme level reporting: our_RAP_service/programme-level-reporting.md
3333
- Service design and user research: our_RAP_service/service-design-and-user-research.md
34+
- Website Release Process: our_RAP_service/rap-release-workflow.md
3435

3536
- Implementing RAP:
3637
- Are you ready for RAP?: implementing_RAP/rap-readiness.md

overrides/partials/footer.html

+1-1
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@
5959

6060
<footer class="footer">
6161
<div class="footer_left">
62-
<a href="mailto:datascience@nhs.net"><p>Contact Us</p></a>
62+
<a href="mailto:england.rapchampions@nhs.net"><p>Contact Us</p></a>
6363
<p>Developed by <a href="https://www.england.nhs.uk/">NHS England</a></p>
6464
<p>
6565
View the project on

requirements.txt

+43-40
Original file line numberDiff line numberDiff line change
@@ -1,31 +1,32 @@
1-
attrs==22.2.0
2-
Babel==2.11.0
3-
beautifulsoup4==4.11.1
4-
bleach==5.0.1
5-
certifi==2023.7.22
6-
charset-normalizer==3.0.1
7-
click==8.1.3
1+
attrs==23.1.0
2+
Babel==2.13.1
3+
beautifulsoup4==4.12.2
4+
bleach==6.1.0
5+
certifi==2023.11.17
6+
charset-normalizer==3.3.2
7+
click==8.1.7
88
colorama==0.4.6
99
defusedxml==0.7.1
1010
entrypoints==0.4
11-
fastjsonschema==2.16.2
11+
fastjsonschema==2.19.0
1212
ghp-import==2.1.0
13-
gitdb==4.0.10
14-
GitPython==3.1.37
13+
gitdb==4.0.11
14+
GitPython==3.1.40
1515
idna==3.4
16-
importlib-metadata==5.2.0
17-
importlib-resources==5.10.2
16+
importlib-metadata==6.8.0
17+
importlib-resources==6.1.1
1818
Jinja2==3.1.2
19-
jsonschema==4.19.0
20-
jupyter_client==7.4.9
21-
jupyter_core==5.1.3
22-
jupyterlab-pygments==0.2.2
23-
jupytext==1.14.4
24-
lxml==4.9.2
19+
jsonschema==4.20.0
20+
jsonschema-specifications==2023.11.1
21+
jupyter_client==8.6.0
22+
jupyter_core==5.5.0
23+
jupyterlab_pygments==0.3.0
24+
jupytext==1.15.2
25+
lxml==4.9.3
2526
Markdown==3.3.7
26-
markdown-it-py==2.2.0
27-
MarkupSafe==2.1.1
28-
mdit-py-plugins==0.3.3
27+
markdown-it-py==3.0.0
28+
MarkupSafe==2.1.3
29+
mdit-py-plugins==0.4.0
2930
mdurl==0.1.2
3031
mergedeep==1.3.4
3132
mistune==0.8.4
@@ -35,33 +36,35 @@ mkdocs-jupyter==0.22.0
3536
mkdocs-material==8.5.11
3637
mkdocs-material-extensions==1.1.1
3738
mkdocs-redirects==1.2.0
38-
nbclient==0.7.2
39+
nbclient==0.9.0
3940
nbconvert==6.5.4
40-
nbformat==5.7.3
41-
nest-asyncio==1.5.6
42-
packaging==22.0
41+
nbformat==5.9.2
42+
nest-asyncio==1.5.8
43+
packaging==23.2
4344
pandocfilters==1.5.0
4445
pkgutil_resolve_name==1.3.10
45-
platformdirs==2.6.2
46-
Pygments==2.15.0
47-
pymdown-extensions==10.0
48-
pyparsing==3.0.9
49-
pyrsistent==0.19.3
46+
platformdirs==4.0.0
47+
Pygments==2.17.2
48+
pymdown-extensions==10.4
49+
pyparsing==3.1.1
50+
pyrsistent==0.20.0
5051
python-dateutil==2.8.2
51-
pytz==2022.7
52-
PyYAML==6.0
52+
pytz==2023.3.post1
53+
PyYAML==6.0.1
5354
pyyaml_env_tag==0.1
54-
pyzmq==25.0.0
55+
pyzmq==25.1.1
56+
referencing==0.31.0
5557
requests==2.31.0
58+
rpds-py==0.13.1
5659
six==1.16.0
57-
smmap==5.0.0
58-
soupsieve==2.3.2.post1
60+
smmap==5.0.1
61+
soupsieve==2.5
5962
tinycss2==1.2.1
6063
toml==0.10.2
6164
tornado==6.3.3
62-
traitlets==5.8.1
63-
typing_extensions==4.3.0
64-
urllib3==1.26.17
65-
watchdog==2.1.9
65+
traitlets==5.13.0
66+
typing_extensions==4.8.0
67+
urllib3==2.1.0
68+
watchdog==3.0.0
6669
webencodings==0.5.1
67-
zipp==3.8.1
70+
zipp==3.17.0

0 commit comments

Comments
 (0)