Specify how/where to identify individuals from a project to join the CPC

[Relequestual]

Part of the onboarding checklist requires that a project to...

Identify individuals from the project to join the CPC

How/where should this be done?
Maybe the project could specify it in a specific repo in their org?
(Is presuming the use of GitHub an OK thing to do?)

Whatever the decision, could this be made clearer in the onboarding checklist so this isn't a question in future? =]

Tracking for JSON Schema: json-schema-org/community#349

[mhdawson]

Identify individuals from the project to join the CPC

There is no specific way mandated in terms of how representatives are elected for impact projects. In the case of non-impact projects it is still good to get people from projects to join the CPC. It would still be up to the project as who/how they would want to encourage to join.

If you have any related questions I'm happy to chat about how we elect representatives in the Node.js project. In terms of encouraging others, it's mostly just by making people aware that it is a possibility for any project member.

[Relequestual]

@mhdawson That's not quite what I mean 😅.
I mean, assuming the project already knows who it would like to represent it, how should it identify them to the CPC?

[mhdawson]

I think they can open an issue to add themselves to the CPC and indicate that they are from project X. Maintainers from that project could then chime in in the issue indicating that they support those people representing the project.