Questions about Committees in PCC

Hi @Kendall_Perez :wave:, Iā€™m sorry for my delayed response. I hope Iā€™m not too late on getting back to you regarding this!

This is a great question. Typically a public TSC mailing list will be comprised of community members to stay up to date on the direction of the technology.

Essentially we would want to ensure we are only defining formal committee members which we can find in most projectā€™s project charter.

This does not mean committee members are the only ones allowed to join TSC meetings or mailing lists

For Magma their project charter states that they have 5 official TSC members, you would just add those 5 members as the TSC for magma and not the 92. The 92 came from the initial groups.io mailing list sync. The charter also speaks on how the mailing list is open to their community.
Governance/CHARTER.md at main Ā· magma/Governance (github.com)

And hereā€™s the list of the 5 official voting members:
Magma TSC Members Ā· magma/Governance Wiki (github.com)

The reason we are defining the committee members in PCC over having it solely updated on a charter in a source control file is because of the streamlined benefits of defining committees in PCC. Which you can read more about here:

Also, the committees defined in PCC are represented in LFX Organization and Individual Dashboard, and although we are all so very humble here :blush: I think everyone can appreciate recognition for their work in open source communities. Great way to keep track of your open source ā€˜online resumeā€™ Technical and non technical :wink:

1 Like