-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial report commit #28
Conversation
Ok this is actually taking longer than I expected, so am just gonna focus now on getting the raw notes uploaded, and then come back to summaries etc. For summaries/next steps, I think Lucy has done some great work on this already (baked into the slides). We just need to flesh out the slides slightly more in these descriptions! I have done one for the Multi-TRE analysis breakout |
Jobs to do:
|
I am going to have to leave soon today, but can have a stab at this tomorrow.
We said we would drop atttendees I think, although open to reconsider at a community level. I see 'Index' already has an updated description and includes the report from the keynote, imo it would be good to also add a bit of a reflection from the day (how happy we are seeing everyone there, hwo we took it as a key point it the life of the community...) |
Ugh Idk why that link check is failing, @manics any ideas? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No time for 3 last files so will come back to it:
- Need anonymisation
- Some copy pasted format causing issues, made the neessary suggestions I hope
- Took out images of handwritten notes, they make it too long
docs/events/wg_workshops/2023-09-04-september-meeting/breakout-ai-ml-llm.md
Outdated
Show resolved
Hide resolved
docs/events/wg_workshops/2023-09-04-september-meeting/breakout-ai-ml-llm.md
Outdated
Show resolved
Hide resolved
docs/events/wg_workshops/2023-09-04-september-meeting/breakout-cloud-onprem.md
Outdated
Show resolved
Hide resolved
docs/events/wg_workshops/2023-09-04-september-meeting/breakout-cloud-onprem.md
Outdated
Show resolved
Hide resolved
docs/events/wg_workshops/2023-09-04-september-meeting/breakout-community-governance.md
Outdated
Show resolved
Hide resolved
docs/events/wg_workshops/2023-09-04-september-meeting/breakout-standardisation-tensions.md
Outdated
Show resolved
Hide resolved
docs/events/wg_workshops/2023-09-04-september-meeting/breakout-standardisation-tensions.md
Show resolved
Hide resolved
...ents/wg_workshops/2023-09-04-september-meeting/breakout-tre-sustainability-and-operations.md
Outdated
Show resolved
Hide resolved
...ents/wg_workshops/2023-09-04-september-meeting/breakout-tre-sustainability-and-operations.md
Outdated
Show resolved
Hide resolved
...ents/wg_workshops/2023-09-04-september-meeting/breakout-tre-sustainability-and-operations.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
final 3 files reviewd, also made suggestions to take out the title 'Attendees' where I had failed to do so.
...ents/wg_workshops/2023-09-04-september-meeting/breakout-tre-sustainability-and-operations.md
Outdated
Show resolved
Hide resolved
docs/events/wg_workshops/2023-09-04-september-meeting/breakout-ai-ml-llm.md
Outdated
Show resolved
Hide resolved
docs/events/wg_workshops/2023-09-04-september-meeting/breakout-cloud-onprem.md
Outdated
Show resolved
Hide resolved
docs/events/wg_workshops/2023-09-04-september-meeting/breakout-community-governance.md
Outdated
Show resolved
Hide resolved
docs/events/wg_workshops/2023-09-04-september-meeting/breakout-ai-ml-llm.md
Outdated
Show resolved
Hide resolved
docs/events/wg_workshops/2023-09-04-september-meeting/breakout-ai-ml-llm.md
Outdated
Show resolved
Hide resolved
docs/events/wg_workshops/2023-09-04-september-meeting/breakout-ai-ml-llm.md
Outdated
Show resolved
Hide resolved
docs/events/wg_workshops/2023-09-04-september-meeting/breakout-ai-ml-llm.md
Outdated
Show resolved
Hide resolved
docs/events/wg_workshops/2023-09-04-september-meeting/breakout-ai-ml-llm.md
Outdated
Show resolved
Hide resolved
...ents/wg_workshops/2023-09-04-september-meeting/breakout-tre-sustainability-and-operations.md
Outdated
Show resolved
Hide resolved
...ents/wg_workshops/2023-09-04-september-meeting/breakout-tre-sustainability-and-operations.md
Outdated
Show resolved
Hide resolved
|
||
- Talk to HDR UK about what they should include in this landscape, and work together with them on co-creating solutions. | ||
|
||
The session ended with a short Q&A, which can be found on the [recording of the session](https://www.youtube.com/watch?v=ipfU4FdjYGM). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you know the timestamp we can include it in the link (append&t=<MINUTES>m<SECONDS>s
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suspect the Turing website is treating GitHub link checks as suspicious traffic and blocking it |
That would be very Turing, @JimMadge have you had a similar issue before? |
docs/events/wg_workshops/2023-09-04-september-meeting/breakout-standardisation-tensions.md
Outdated
Show resolved
Hide resolved
This PR is too big and has been open too long 😄 I think the best approach now is to get any final changes in, and when we're happy with the content I'll rebase this branch, squash, and force push, to remove all history (so we'll end up with a single commit) before merging |
Definitely! I am now struggling with changes from everyone. Agreed, let's finalise content which I think we are happy with? I will approve your suggestions @manics they all LGTM |
I've marked this as draft as a reminder to force push/rebase to remove the history. I'll do that as soon as someone tells me to 😄 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Harmonised title hierarchy: roadmap and quesitons were someitmes wihtin raw notes sometimes not, they should be as they are titles from the hackmd templates
docs/events/wg_workshops/2023-09-04-september-meeting/breakout-cloud-onprem.md
Outdated
Show resolved
Hide resolved
docs/events/wg_workshops/2023-09-04-september-meeting/breakout-cloud-onprem.md
Outdated
Show resolved
Hide resolved
docs/events/wg_workshops/2023-09-04-september-meeting/breakout-cloud-onprem.md
Outdated
Show resolved
Hide resolved
docs/events/wg_workshops/2023-09-04-september-meeting/breakout-community-governance.md
Outdated
Show resolved
Hide resolved
docs/events/wg_workshops/2023-09-04-september-meeting/breakout-community-governance.md
Outdated
Show resolved
Hide resolved
docs/events/wg_workshops/2023-09-04-september-meeting/breakout-satre.md
Outdated
Show resolved
Hide resolved
docs/events/wg_workshops/2023-09-04-september-meeting/breakout-standardisation-tensions.md
Outdated
Show resolved
Hide resolved
...ents/wg_workshops/2023-09-04-september-meeting/breakout-tre-sustainability-and-operations.md
Outdated
Show resolved
Hide resolved
...ents/wg_workshops/2023-09-04-september-meeting/breakout-tre-sustainability-and-operations.md
Outdated
Show resolved
Hide resolved
...ents/wg_workshops/2023-09-04-september-meeting/breakout-tre-sustainability-and-operations.md
Outdated
Show resolved
Hide resolved
As soon as I said content was good I noticed titles were quite inconsistent... should be good now? @manics if you like how it looks now commit (or tell me to) and go ahead with the GHmongery? |
Welcome, keynote and lightning talks Initial structure Keynote summary Lightning talks Multi-TRE analysis breakout TRe sustainability and operations breakout Breakout - Python & R PPIE breakout SATRE breakout Standardisation tension breakout Data harmonisation breakout Final breakouts AI/ML approach notes TRE sustainability Allowlists PPIE On prem vs cloud NHS SDEs SATRE standardisation tensions Data harmonisation Sight unseen Community governance TOC tree Fixing broken link Fixing broken link v2 Apply suggestions from code review Co-authored-by: Davsarper <[email protected]> Run pre-commit linkcheck_ignore: https://www.turing.ac.uk/ Remove attendee names Co-authored-by: Davsarper <[email protected]> Code review changes pre-commit Update docs/events/wg_workshops/2023-09-04-september-meeting/index.md Co-authored-by: Simon Li <[email protected]> Update docs/events/wg_workshops/2023-09-04-september-meeting/index.md Co-authored-by: Simon Li <[email protected]> Apply suggestions from code review: heading levels Co-authored-by: Davsarper <[email protected]>
c6d3fda
to
7d2e165
Compare
docs/events/wg_workshops/2023-09-04-september-meeting/breakout-sessions.md
Outdated
Show resolved
Hide resolved
Yes, not just GitHub. In general I don't think I've found a link checker that works out of the box. I think the webserver rejects requests that don't have the headers saying they are a browser. It might work if you spoof Firefox, for example. But I generally add |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apologies if my 'this works for me' file naming and structure made this harder than it needed to be... and if it did plz lmk how to improve in the future! |
No description provided.