Selection of host sites for ProgCode fundraising

[stephenscapelliti]

Challenge: Select fundraising platforms which are consistent with the values and mission of ProgCode.

Description

This initiative seeks both input and approval from the ProgCode community for the identification, selection, and implementation of fundraising sites by which to solicit small dollar donations.

Problem

1. Fundraiser websites are a convenient tool for the small dollar donation component of funding ProgCode operations. Terms of service and available features differ from site-to-site, and usage costs vary.

2. Consistent with ProgCode values and stated community preferences, the selected fundraising platforms should be independent of any electoral political party and consistent with the mission to reduce the influence of money in politics. The site should link to the ProgCode credit union account and/or to the debit card associated with the account. The donation process with respect to a particular site should not impose unusual or onerous obligations on ProgCode staff, other than ordinary accounting functions.

3. No agreement between ProgCode and a fundraiser site or service should result in the payment of a fee, commission, or other remuneration by the fundraiser site to any member of the ProgCode community. This does not restrict ProgCode from entering into a separate compensation agreement with any member or non-member for fundraising services.

4. Examples of fundraiser sites include Crowdpac and Patreon. Both allow for donation subscriptions, usually on a monthly basis, as well as one-time donations. A Patreon account has been created for ProgCode, but has not been published pending consideration of this pilot initiative.

Benefit

This will enable ProgCode to commence small-dollar fundraising activities consistent with the policy of community decision-making.

Plan

• [ ] Post this pilot initiative and notify the ProgCode community in the #team-announcements and #operations channels. Request that suggestions be offered in the comment sections below this issue, for future reference.
• [ ] Present the issue for discussion at the 12-11-17 Community Operations meeting, and seek consent to proceed.
• [ ] Seek consent to implement at the 12-18-17 Community Operations meeting, with respect to each separate fundraiser site identified.
• [ ] ProgCode staff will be responsible for set-up and implementation of the relationship between ProgCode and each fundraiser site approved by the community.
• [ ] ProgCode staff shall report the completion status of each fundraiser site relationship to the community in the #team-announcements and #operations channels.
• [ ] Upon completion, this issue shall be closed, but may be reopened and the foregoing implementation process utilized for adding/substituting other fundraiser sites identified in the future.

Decision Making

As stated above, consent to proceed will be requested at the 12-11-17 Community Operations meeting, and consent to implement will be requested at the 12-18-17 Community Operations meeting.

Optional Information

Reference link(s)

Issue #81 - Funding Framework ProgCode Funding - One-Pager ProgCode Funding Use Cases - Revenue

[PamelaJohn]

@stephenscapelliti This looks great!! My only question is with regard to item 3:

No fundraiser relationship should result in a personal financial benefit to any member of the ProgCode community.

The wording here seems a bit too general in that it might be construed to conflict with using fundraisers to pay the salaries & benefits of future staff members. Is there a way to make a more specific reference to the type of fundraising relationship you're referencing?

[PamelaJohn]

@stephenscapelliti In planning for the website update to include a donate button and About section which discusses our 501(c)(4) status, I reviewed the staff work hour notes of 2017.11.29 and see that we intended this Git Issue to contain the following information:

Update/Edit Guidelines to include a section front and center about Non-Coordination Policy

• Stephen will create a GitHub Issue to update ProgCode Community Guidelines
• Perhaps include something like a three-strikes process for notifying members who accidentally or repeatedly breach the rules/guidelines. ✔ Stephen created GitIssue #227

[PamelaJohn]

@stephenscapelliti I'm not sure if all of the boxes under "Plan" have been checked off. If so, is it okay to close this issue?