ProgressiveCoders/functions

Define Vetting process and implement

Opened this issue · 3 comments

StraubCreative commented

Required Information

Description

With the creation of new #vetting channel in ProgCode Slack, the actual vetting procedure has yet to be defined and implemented.

Problem

Currently, there are no formal nor communal safeguards in place that assess the integrity of external working relationships with or within ProgCode. This leaves the community and it's leaders open to possible

  • cooptation efforts from outside political or partisan forces
  • violations in ProgCode Staffers Policy & Guidelines
  • legal violations in holding 501(c)4 status

Benefit

The vetting process acts as a community safeguard against outside political or partisan groups that may want to work with ProgCode by addressing essential screening criteria for present and future working relationships, which include but are not limited to:

  • Funding sources
  • Known Affiliates
  • Work History
  • Political Affiliations or Partisanship?
  • Point Person(s)
  • ...and so on

The vetting process, while community driven, may act as an essential tool in the Evangelist's kit to promote and protect the integrity of ProgCode Staffers Policy & Guidelines. Related #199

Plan

  • Zachary Straub to generate basic blueprint for vetting process
  • Community Supermajority Vote to Proceed
  • Zachary Straub to share updates, revisions, and drafts in #vetting channel
  • ProgCode administrative team and community offer suggestions and revisions as needed
  • Final draft/model goes to a Community Supermajority Vote to implement (10 votes required)

Decision Making

by-consent and by-network-vote

Optional Information

Reference link(s)

StraubCreative commented

5.17.17 Update:
I'm planning to create a demonstrable vetting model for the #operations meeting on Monday, May 29th.

Goals:

  • Showcase how an efficient vetting model can be created and sustained with a community-driven agile workflow "ticket" system, with documentation and sustainability plan.
  • Provide live demonstration to how this vetting model would function, demonstrate vetting procedure.
  • Answer any questions the community may have about agile workflows or vetting procedure.
  • Provide opportunity for PC operations + community to contribute their ideas to vetting model before and after votes to proceed and eventually implement.

I will be posting updates in #vetting channel and in #discussion.

rcscastillo commented

This is beautiful Zac! I'm really excited about this.

One thing I'd like to raise is that of instances of mixed legal structures (an organizations having a PAC & a 501(c)4, etc).

StraubCreative commented

Thanks Rapi!

Agreed. There's definitely going to be some case-by-case situations I think. For this first step, it would be us saying "let's get a functional model up and tweak it as needed" to accommodate special situations and IRS guidelines.

Updates this week :D