Announce that Codespaces are generally available

[iaindillingham]

We should announce that Codespaces are generally available. This means we should do the following tasks, in this order:

• [x] Introduce Codespaces at the Co-Pilot Deep-Dive on Tuesday 28th May, 2pm.
• [x] Meet with co-pilots on Thursday 6th June, 2pm to discuss Codespaces: answer questions, listen to concerns.^1
• [x] Answer questions at the user-group meeting on Friday 14th June, 10am.
• [x] Answer questions at the Co-Pilot Deep-Dive on Friday 14th June, 1pm.
• [x] ~Introduce Codespaces at the Bristol-Cambridge-Oxford meeting on Thursday 4th July, 11am.~ The July meeting was cancelled. It's likely that the August meeting will be cancelled, too. Whilst we should introduce Codespaces during a Bristol-Cambridge-Oxford meeting, doing so shouldn't block the initiative.

We should then do the following tasks, in this order:

• [x] Give a team talk at Team Talks and Weeknotes on Tuesday 9th July, 12pm.
• [ ] Add a summary to Platform News.
• [ ] Add a short message with a link to "How to add GitHub Codespaces to your project" and "How to use GitHub Codespaces in your project" to #opensafely and #opensafely-users.

Points to communicate

For more information, see "Co-Piloting in Codespaces".

[iaindillingham]

I've asked what format would work best for co-pilots in #co-pilot-support.

[iaindillingham]

Remember to ask one or two co-pilots whether we can observe them walking through "How to add GitHub Codespaces to your project".