Clean up issues for open source

[gsproston-scottlogic]

Clean up existing issues, keeping in mind that we're going open source.
Have a meeting where we run through all the issues together.

Tasks:

• Only keep issues that we want people to work on. We don't want developers picking up tickets that we have no intention of pulling into the code.
• Label simple issues with "good first issue".
• Simplify labels.
• Ensure there's nothing sensitive in the tickets/PRs, including closed ones! - maybe leave out PRs for now. Go through issues by date or label.

Questions:

• What to do with the remote deployment tickets? Is it ok to keep them? - fine to keep

TEAM EFFORT
Keep track of who is reviewing what - comment below "I am reviewing tickets number 1 to 20 etc"
Comment any unsure tickets

[pmarsh-scottlogic]

Issues/PRs:
#1 to #100 ✅ by Peter
#101 to #200 ✅ by George
#201 to #300 ✅ by Peter
#301 to #400 ✅ by George
#401 to #500 ✅ by peter
#501 to #600 ✅ by Heather
#601 to #629 ✅ by George

[pmarsh-scottlogic]

Extra things to check / remove:

• old mural board (linked to by Application face-lift #40) [checked by Peter]
• figma board (linked to by Application face-lift #40 ) [checked by Peter]
• Comment on 241 support more characters in exported logs #247 about checking the licenses for our fonts - made Add OFL text #631 to track this.
• Other project name mentioned here
• Link to google doc here, though I expect that's ok as it should be restricted.
• Other project mentioned here.
• And here.