Private Channels

[jpb5013]

Required Information

Description

Proposal to address multiple private channel items, including:

• Create a private channel for ProgCode contributors
• Remove existing private channels besides #recruitment and #team-leads
• Disable private channel creation
• Update GitHub Wiki ...

Problem

Several reasons:

• While maintaining transparency, there should a private space to discuss private items before the broader ProgCode community
• There are several dormant private channels
• We are exposed to legal risk by allowing un-checked private channels
• We do not have a public-facing policy/process for private channels ...

Benefit

People will have better understanding of how ProgCode works, ability to discuss with other contributors, and acknowledgement for regular contributors ...

Plan

• [x] Discuss in operations team meeting
• [ ] Update Wiki article
• [x] Create pcn-contributors channel
• [ ] Respond to this issue for included people
• [ ] Supermajority vote to add new people handled in third-party application
• [ ] Update Slack to remove private channel creation
• [ ] Update Slack to archive dormant channels
• [ ] Add if someone commits to volunteer five minutes or more here ...

Decision Making

Consent to implement ...

Optional Information

Reference link(s)

...

[PamelaJohn]

10.16.2017 Consent to Implement sought. 10.19.2017 Consent to Implement approved by the community without objection. This change can be implemented per the ProgCode Change Process.

[PamelaJohn]

At the 10.16.2017 meeting, David Jay raised some great adjacent questions which the body didn't fully address but which would be good to address in the updated functions Wiki re: the #pcn-contributors private channel.

It's a good idea to have a private space to discuss any community members who may not be abiding by community norms. Some questions which arise are: 1) What actions are to be taken, if any; 2) Who is allowed in that private space, how are those decisions made, how is communication made within the community? 3) What is the process for creating new private channels (i.e., is it just a vote in the Operations Meeting?) and is there a norm about how information stated in private channels is shared (i.e., Fight Club Rules: what's said in the private channel stays in the private channel.)

The above text is posted in the new #pcn-contributors channel for discussion & updating the Wiki. (Tagging in @jpb5013 because you've got access to the Wiki)

Notes from the 10.16.2017 Ops Meeting

[PamelaJohn]

Also at the 10.16.2017 meeting, Josh Cohen at OSDI invited ProgCode members to help codify a policy of Conflicts Resolution & Code of Conduct. They appointed VP of Diversity & Inclusion, Sonya Reynolds, and formed a committee to work on this issue. There's a need for a common description of isolating behaviors that exclude people as well as offensive behavior and a conflict resolution policy to take an inclusive approach for restorative justice and concessions which need to be made. Josh is doing recruiting for Sonya but she will take the lead on secondary steps.

[jpb5013]

I am interested in joining and would like to commit 5 minutes or more per week

[adcor]

I am interested in Joining nd would like to commit 5 minutes or more per week.

[PamelaJohn]

Ditto, I'm interested in joining the private channel and commit to contributing at least 5 minutes per week of my time to volunteer at ProgCode!

[stephenscapelliti]

I will commit at least 5 minutes per week for the ProgCode community.

[PamelaJohn]

2017.11.01 - Jody DM'd and would like to be added to the list. She will commit at least 5 minutes per week to volunteer for the ProgCode community.

[I'll see if she wants to set up time for a quick GitHub tutorial!]

[jpb5013]

David Jay signed up for the volunteer sign up sheet, adding to channel