Skip to content
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

First draft for a meeting chair guide as inspired by Holger. #103

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

mkurzman
Copy link
Collaborator

Hi Frances, Jan, Oliver,
Holger is so nice to take over the chair for 15th of december 2023 and asked me for a guidance.
I thought it would be a good idea and tried to collect some experiences I made.
Please check it and your input would also be welcome to get a good guidance document.

BTW: BigBlueButton still does not work for me as a moderator yet or I do not know how to use it properly.

Thank you.

@jthDEV
Copy link
Collaborator

jthDEV commented Nov 15, 2023 via email

Copy link
Contributor

@OliverFendt OliverFendt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mkurzman great contribution, I have made some small comments. I further changed the settings of the bigbluebutton conference room - now every attendeee shall have moderator rights and thus should be able to start the recording - can you please verify?

Meeting-Material/readme.md Outdated Show resolved Hide resolved
2. (optional) Ask / inform all participants for consent for recording and turn the cameras off. Start recording
3. Show the Antitrust slide from OpenChain and inform about the Antitrust requirements (e.g. "Stick to the shared agenda", ...).
4. Take notes in the yyyymmdd.md in the branch set up above in "2."
5. Collect all participant names in the notes.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this needed?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When I made the first *.md-file I tried to copy structure from a good practice so I went to the SPDX-community: https://github.com/spdx/meetings/tree/main/general
They have this section but tbh I had the same question but didn't have the time yet to ask them nor did I have the time to check if our internal antitrust requirements would require that transparency (If we manage to come back to record the meetings, the whole meeting would be anyway transparent).
I tried it out in my sessions to list the names and with MS Teams it was rather easy to collect the names but it is additional effort to invest. So I appreciate that you brought up this point. Also the agenda-point of "approving" the minutes of the last meeting seems to me very formal, but on the other hand the SPDX-meeting documentation is really crystal clear :-)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mkurzman thank you for the explanation. I would not regard this as mandatory. Approving the minutes I would not introduce. We are an open group and persons who participated in meeting a might not be present in meeting a+1 who will be empowered to approve the minutes in this case. I think this is overhead with zero value, so lets skip it.

Meeting-Material/readme.md Outdated Show resolved Hide resolved
Added the link to the *.pptx. Potentially in the next version might make sense to also link a PDF for non-MS Users.
PDF for slides instead of links
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants