docs: updates communication details in README.md

[jpower432]

Types of changes

• Hot fix (emergency fix and release)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Documentation (change which affects the documentation site) (README.md)
• Breaking change (fix or feature that would cause existing functionality to change)
• Release (develop -> main)

Quality assurance (all should be covered).

• My code follows the code style of this project.
• Documentation for my change is up to date?
• My PR meets testing requirements.
• All new and existing tests passed.
• All commits are signed-off.

Summary

Updates Community meeting details in README.md

Key links:

• Sonar coverage

Before you merge

• Ensure it is a 'squash commit' if not a release.
• Ensure CI is currently passing
• Check sonar. If you are working for a fork a maintainer will reach out, if required.

[jpower432]

This is in draft pending the addition of the notes link only. Other changes can be reviewed in the meantime.

[AleJo2995]

LGTM. I have updated the convert time tool as the previous link didn't work

[mrgadgil]

LGTM.

[degenaro]

re: lint fail

This is annoying. I had the same problem in #1533. I fixed by changing id to id_ in 2 places. This will be further annoying when #1533 is delivered to develop if there's a conflict. Ugh.

[AleJo2995]

@degenaro Do you know why is this happening in the end? I'm applying the fix temporarily because we need to merge this details before tomorrow's call, but I haven't found a reason either. And what I see is weirder is that locally I'm not being able to reproduce it

[jpower432]

Thanks for adding the fix @AleJo2995. CI is passing now, is this good to merge?