I would like to schedule an upcoming Hyperledger Marketing Committee meeting using PCC Meeting Management.
I have linked the mailing list marketing@lists.hyperledger.org to the Hyperledger | Marketing Committee committee. I would like all subscribers (280+) of the marketing@lists.hyperledger.org mailing list to receive the meeting invite and zoom details; however, it seems the meeting management tool only pulls up the 9 voting reps of the committee. I have a few questions:
How do we make sure the meeting invite gets sent to all current 280+ subscribers of the marketing@lists.hyperledger.org mailing list? Marketing Committee rarely has to vote on anything, we tag the voting members on Marketing Committee to comply withe the charter requirement. This committee is really about participation and engagement. So itâs important that we make sure when we schedule a meeting, the invite/zoom details is sent to all subscribers.
Hyperledger membership changes all the time, with new members joining and existing members cancelling and marketing contacts changes all the time. Currently, groups.io allows admins to add and remove subscribers from restricted lists such as the Marketing Committee mailing list. We turn on the âsend invite upon joinâ on calendar in groups.io and set up event âremindersâ so that scheduled meeting invites are always sent to the new and current group subscribers. How does that work in PCC Meeting Management?
Is the PCC Meeting Management also to be used for open technical community meetings as well? If so, itâs confusing that weâre sending the meeting invite to âCommittee Membersâ and that we are limited to select groups tagged as type of âCommitteeâ. Would âgroup membersâ be more encompassing? And then in the âSelect Committeeâ drop down, users should be presented with all the groups that have been established for the project to select from to schedule the meeting for.
Adding @Daniela_Barbosa for visibility since Hyperledger is eager to try Meeting Management but seeing some challenges.
You can use meeting management to invite any member of your community as long as they have an LFID.
@emsearcy, or @ProdMgrs do you know if there is any current workaround for inviting 280+ members associated to a mailing list using meeting management?
There was a mandate for us NOT to use mailing lists as a âgroupâ for meeting invites â this is a larger story, but basically mailing lists donât have metadata to understand what peopleâs engagement/role is, which is what committees are for, and we allow committees to sync/push into groupsâso capturing any âofficialâ grouping of community members is recommended to be done on a committee. For instance, not just for boards and TSCs, but also for projects that maintain an official list of maintainers/committersâthere should be a committee for that, not just a mailing list.
That said ⌠Iâm assuming this might be a public, open mailing list for community members (anyone can join?), and that the meetings are also therefore open? Assuming so, instead of thinking of inviting every self-subscribed member of the list as a de-facto meeting participant, you can share, with your mailing list, a URL that the community can use to self-register for the meeting. Currently you can grab this URL out of the text of any emailed meeting invite, but we are also adding a pop-up in PCC (which I suspect will release in the next 1 to 2 weeks) to share the URL with the PCC admin so you can easily copy it and share it to the community. (Public community-facing calendars of all public project meetings is on the roadmap, too.)
There are two significant differences between sharing the self-registration URL, and directly adding every list member as a participant. The first is attendance statistics - if you add every list member as a participant, theyâll also affect participation stats as âno showsâ. With the URL, only those that opt-in to register for the meeting will affect âno showâ stats. Second, is how many emails they get. Registered participants will get an email every time the time changes, for example, and (in the future) can have meeting reminders sent to them en masse using PCC. Using the self-registration URLs cuts down on âspamâ for any members of the broader community â theyâll only get automated meeting-related emails if they self-subscribed to the meeting.
It would be helpful to have a documentation that describes the meeting invitee journey/flow that cover elements such as: notifications, LFID requirement/flow, meeting registration process, adding meeting to their calendar, what to expect if the event changes/cancels and what-if scenarios and how to get support. Or maybe this is available? if so, could you please point me to the documentation?
You can access support, for reported bugs/issues on the top right of every LFX Tool:
The community forum, is best for what-if scenarios, as we want to hear from our users so our product dev team can best optimize the tooling for our userâs use cases.
For instance⌠this is great feedback I can relay to our product dev and documentation team.
Would you prefer a quick demo video or more documentation on meeting managements user journer?
Thanks @Henry_Quaye ! Yes, I have looked at those documentations. Those are from PCC admin/user perspective.
However, I am specifically asking for documentations for what a meeting INVITEEâs journey would be like (email notifications they will get, LFID signup process, meeting registration process, how to add meeting invite to their calendar, what happens if the meeting is changed or cancelled, different process for those who are direct invites vs registering with a shared link as Eric was saying). So that we know what to expect and can help field questions if our members or communities have questions. The risk is much higher when we donât know the journey/process from the meeting inviteeâs perspective and thus unable to help our members and communities.
