Description
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