I think it's important to define the term more clearly to get good answers.
Is every Teams/Slack/Zoom call with more then one more person a meeting? Even if the context/content is preparing/planning/pairing on a ticket?
When there are team rituals, is the length and frequency working for the goals that the ritual is trying to reach?
And last but not least, are the right people invited? Minimize "mandatory meetings" and if a whole group is invited, make it clear (over and over again) when a "relevant discussion" is only for the people that are interested.
And be brave about giving feedback to organiser(s) or even saying "No" if you think it's not relevant for you.
I think it's good to regularly think about/question those things, in a way that's a hygiene thing.
By the way, providing meeting notes for people that didn't have the chance to join makes it easier to jump on and off, or get involved when it's relevant.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think it's important to define the term more clearly to get good answers.
Is every Teams/Slack/Zoom call with more then one more person a meeting? Even if the context/content is preparing/planning/pairing on a ticket?
When there are team rituals, is the length and frequency working for the goals that the ritual is trying to reach?
And last but not least, are the right people invited? Minimize "mandatory meetings" and if a whole group is invited, make it clear (over and over again) when a "relevant discussion" is only for the people that are interested.
And be brave about giving feedback to organiser(s) or even saying "No" if you think it's not relevant for you.
I think it's good to regularly think about/question those things, in a way that's a hygiene thing.
By the way, providing meeting notes for people that didn't have the chance to join makes it easier to jump on and off, or get involved when it's relevant.