Closed lexnederbragt closed 5 years ago
@lexnederbragt I don't think you're misinterpreting/overinterpreting. I think we are so used to everyone being involved that we hadn't really considered how this would impact people we get on the EC for the expertise we need but who aren't active community members.
Is it appropriate to apply this to community-elected members and not EC-elected members?
I think this is a valid concern @lexnederbragt has raised. I not personally in favor of differentiating responsibilities between community and council elected members, but am amenable to reframing the language so that it clarifies what this means. In my mind, this means that EC members are expected to engage in the general events of the community, which includes things like reading the newsletter and attending community calls when applicable.
I've removed that sentence from the page linked above, which allows the language to reflect that present on the main website.
Closing this, as it appears to have been adequately resolved.
The https://github.com/carpentries/executive-council-info/blob/master/process/roles_responsibilities.md currently states (emphasis added)
To me this looks like it formalises active membership in the community (being an active instructor, trainer, mentor, maintainer, ...) as part of being on the EC. This could pose a problem for those interested in joining the EC as council-elected members from outside the organisation.
Am I misintrepreting/overintrepreting the phrasing, or should we adjust it?