software-engineering-quality-framework issues

Update security-repository.md

1

The guidance around Teams setup is incorrect. - Child teams cannot have their visibility set to secret. - CODEOWNERS file will not work with secret teams. Altered markdown to reflect...

LouPritch

Publishing/Open Source guidance too strict

2

In the open source guidance in this framework it says that code must have unit tests, integration tests, API tests and more besides. https://github.com/NHSDigital/software-engineering-quality-framework/blob/main/quality-checks.md?plain=1#L66-L86 This contradicts other guidance released by...

adam-carruthers

Expand on serverless architecture deployment strategies

1

@stefaniuk raised some interesting points around considerations for Servless architecture deployment strategies. https://github.com/NHSDigital/software-engineering-quality-framework/pull/291#discussion_r1137723837 It would be useful to explore these further.

walteck

added example of github pushing to s3, using oidc

1

dlavender4

Add guidance around game days

It would be useful to agree additional guidance around how to approach and implement game days and when to use them.

walteck

Adding links to accessibility checklist Closes #282

1

Added a link to the NHSD Accessibility Checklist in: insights/review.md practices/continuous-integration.md quality-checks.md

nicksp1

documentation

Add link to NHSD Accessibility checklist on appropriate pages (quality checks, review and continuous-integration)

A new NHS Digital accessibility checklist has been created and approved for general use. Include it in various places within the SEQF to provide accessibility guidance to teams. (https://nhsdigital.github.io/accessibility-checklist/)

nicksp1

documentation