Define Core CommComm Values

[bnb]

Per the work being done in documenting expectations of both TSC and CommComm leadership (nodejs/admin#12 and nodejs/admin#12 (comment)), I'd like to kick off a Values definition for CommComm.

Ideally, this will be several simple bullets that cover the various things that the CommComm holds as values. I think building out a first draft and shipping it would be a good start - we can iterate over time as much as is needed 👍

[hackygolucky]

Should we try to do an online working session(maybe 1 hour) with this akin to what we did at Collab Summit? There's free software that plays like sticky notes on a white board that we could work with, and then we're getting a more genuine result from individuals.

[rachelnicole]

that sounds like a good idea Tracy

…

On Wed, Oct 25, 2017 at 2:53 PM, Tracy ***@***.***> wrote: Should we try to do an online working session with this akin to what we did at Collab Summit? There's free software that plays like sticky notes on a white board that we could work with, and then we're getting a more genuine result from individuals. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#156 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAN7hnZBx_fyfzwJ1K6gEqjs26H-MCNWks5sv4OXgaJpZM4QGaQ2> .

[bnb]

@hackygolucky Love that idea. 💥

[mhdawson]

+1

[Tiriel]

Although I'm not a member, just wanted to let you know you definitely have my +1

[dshaw]

🙌 Interested in joining the CommComm Core Values session.

[bnb]

Going to leave this on the agenda for tomorrow's meeting with a TODO of getting a meeting time/plan of action for this nailed down.

[jemjam]

Hi there! I'd be stoked to help out or participate too. This is great.

[komawar]

would like to add my two cents (&be helpful)

[sarahnovotny]

Are the CommComm's values substantially different from the core project values? It might make more sense to push the core project value conversation to conclusion and then identify where commcomm is different instead of doing independent value exercises.

[mikehostetler]

Agree with @sarahnovotny here. Values are an incredibly important and core part of any organization and it seems that CommComm would inherit the values from the TSC or the Board (please excuse my naiveté here).

Additionally, it strikes me as an anti-pattern that the CommComm would potentially have different values than others in the Node Foundation. If the CommComm finds that one of their values is not represented, the best solution would be to advocate to represent that value across the entire group.

EDIT: Re-reading the initial issue, was the intent to collect values from CommComm members that would be communicated to the TSC, to aid in their exercise of defining values for the entire organization?

[bnb]

@sarahnovotny @mikehostetler This discussion stemmed from the discussion around the expectations doc, linked in the original comment (references: nodejs/admin#12 (comment), nodejs/admin#12 (review), nodejs/admin#12 (comment), nodejs/admin#12 (comment), nodejs/admin#12 (comment), nodejs/admin#12 (comment), nodejs/admin#12 (comment)).

This was an effort to follow through with the discussions and actions suggested in that issue on the side of the CommComm. That same effort (to the best of my understanding) would be parallelled by the TSC, independently (hopefully that answers your question @mikehostetler).

I agree that an overall values doc is more valuable than fragmented values docs.

@Fishrock123 @mhdawson @williamkapke I'd like to ask: Has there been any update on a values doc from the TSC? If not, I'd like to propose that we work together in the nodejs/admin repo to define a minimum (and non-fragmented) set of values for the project.

[mikehostetler]

@bnb Thanks for the background!

[mhdawson]

There has not been work on specific TSC values yet.

My understanding of the concept of having values for a particular group was that they would be more specific to the focus of that group (ie additive versus being in conflict) versus the more general values that apply across all of the groups. For example in groups that focus on code a value might be "test-driven development" which would not be applicable to other teams.

In any case its a bit hard to see were the line between general/group might be until we have the top level ones in place. I think we had discussed trying to get an initial version of those documented to give people a more concrete idea of what they will look like.

[bnb]

Closing this in favor of the Node.js Values efforts happening right now. We can reopen something similar in the future if we need something additive to those efforts 👍