search

nodejs / community-committee

The Node.js Community Committee (aka CommComm)
MIT License
263 stars 70 forks source link

Q&A with Tierney Cyren @bnb – CommComm Chairperson Election #521

Closed amiller-gh closed 5 years ago

amiller-gh commented 5 years ago

CommComm Chairperson Q&A session for Tierney Cyren!

Feel free to drop your questions for @bnb here as comments.

CANDIDATE STATEMENT

As we move into a period where we're exploring the OpenJS Foundation as a container for Node.js, there are a lot of new efforts that we as a committee can and should be working towards. Be it governance updates to make the committee more welcoming, new efforts directly within the GitHub org, building out tooling that leverages new features of our one and only platform (GitHub), there's a lot of work that can and should be falling under the Community Committee.

One of the most important things for me personally is to ensure that the CommComm is able to remain fresh. I personally feel that we need to address membership and community engagement. Obviously, engagement in Node.js isn't something everyone who uses Node.js has time for. That said, I don't personally feel like CommComm has the activity that I would have expected it to when was originally formed. There are multiple parts here that I would like to try to improve:

  • Diversity of membership of the CommComm. Despite the diversity of the Node.js community, we have overrepresentation of certain groups in the membership. I'd like to talk with former members who weren't from the overrepresented groups and get their feedback on why they've stopped participating and – if they're willing/able – ask what we could do differently to resolve. Beyond that, I'd like to work with the CommComm to bring active community members who are from groups that are not currently represented in the committee and get them involved as collaborators and members.
  • Work collaboratively on more projects. There are so many things we could be doing to improve Node.js and get more people involved in various ways.
    • I'd personally like to see us help the Node.js GitHub organization embrace GitHub Actions by adopting/shipping some Actions that are focused at being welcoming and improving collaborator experiences, in addition to possibly creating content rollups for something like Good First Issues across the organization.
    • I'd also like to see us brainstorm together to see what kinds of things we could do to be more effective in helping to improve the community, going beyond normal status updates. Identifying what others are doing well (for example, noodling on how we could scale something like Gatsby's Swag for Contributors).
  • Be more nimble with policy change. We used to have to go through a lot of work to change policy. Theoretically, this should be a lot easier since we just need to go to the OpenJS Foundation's CPC. This means we don't need to wait months anymore to actually effect widespread change in How We Do Things™. One example of this that I'd like to see rapidly evolve is membership policies – specifically how we handle members who do not participate, making this an easier and more automatic process since there are now very different mechanisms that we as a committee have agreed upon (like Emeritus status) when compared with what existed when those policies were written.
amiller-gh commented 5 years ago

Closing since election is over 🙏