Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standard Change - Grant Research Budget Proposal #262

Open
7 of 9 tasks
stephenscapelliti opened this issue Jul 23, 2021 · 0 comments
Open
7 of 9 tasks

Standard Change - Grant Research Budget Proposal #262

stephenscapelliti opened this issue Jul 23, 2021 · 0 comments

Comments

@stephenscapelliti
Copy link
Member

stephenscapelliti commented Jul 23, 2021

Description

This is a proposal to authorize the procurement of grant research and writing services for Progressive Coders Network II.

Problem

The ProgCode community is transitioning from 501(c)(4) status to 501(c)(3) status. One purpose of the transition is to better qualify for monetary grants that will help fund the ProgCode mission and operations. Individual donations have been consistent but will not rise to the level necessary to fund operations as anticipated in budget needs projections. The community has considered supplemental funding sources such as foundation grants and government grants.

Benefit

ProgCode may apply for such grants through the volunteered services of our members or through the use of outside vendors and contractors. ProgCode has sought foundation grants in the past and - despite qualifying for both activities and mission - was declined funding due to its 501(c)(4) designation. There is a substantial learning curve for these activities, and our effort could benefit from the assistance of experienced grant researchers and writers who can find and match available grants to the ProgCode mission and activities.

Expenditure Analysis

ProgCode member Alex Kotch introduced our community to Justin Spees, an independent grant researcher who has been assisting nonprofit OptOut News to seek grants for its operations. On July 23, 2021, Joe Breslin and Stephen Scapelliti met with Justin and provided him with background on the ProgCode community, mission, and projects. Justin immediately identified one potential funding source for our community.

Following some additional questioning and vetting on behalf of ProgCode, we asked Justin whether he felt he could assist the community in seeking some grants. Justin proposed that he would research up to ten foundation grant sources, using the information we provided him, and provide ProgCode with the grant information. Instead of his usual hourly fee, he would charge ProgCode $100.00 for this one-time service. ProgCode either may apply for the grants using its own resources or retain Justin for additional services to assist ProgCode in applying for the grants.

This proposal seeks authorization for the Board of Directors for a budget of One Thousand and no/100 Dollars ($1,000.00) to research and otherwise seek sources of foundation and/or government grants for and on behalf of ProgCode. If approved by the community, $100.00 of the authorized funds would be paid to Justin Spees in accordance with his offer to identify up to ten (10) grant sources. The remainder of the budget would be committed to future grant research and writing, in the unanimous discretion of the Board of Directors, with a minimum of one week of written notice to the ProgCode community prior to committing to the expenditure. All such additional expenditures will be added as amendments to this proposal.

AMENDED 2022.05.05 - ProgCode retained the services of Justin Spees, as directed by the community through approval of this proposal. Justin has issued detailed invoices for his services which have been paid as follows:

2021.08.13.........$100
2022.02.28.........$150
2022.03.31.........$255
2022.04.30......+$315 = $820

Initially, he identified 18 potential funding sources for ProgCode, as agreed. Since ProgCode received its IRS determination letter granting 501(c)(3) status, Justin has done outreach to more than 40 prospective funding organizations on behalf of ProgCode. He also has contacted finders who seek out mission-aligned projects on behalf of funding organizations. Justin's insights and counsel have benefitted ProgCode in its funding activities.

As the payment detail indicates, there remains $180 available for Justin's services from the authorized $1,000 of funds. Given the amount of progress, extending the contractual relationship with Justin seems prudent. Accordingly, this proposal is being amended to seek consent to implement the authorization of an additional $1,000.00 to be used consistent with the other provisions herein.

Criteria:

  1. A grant researcher and/or grant writer qualified and skilled in identifying mission-aligned foundation grants or government grants for which ProgCode is reasonably likely to qualify.
  2. Identification of such grants by the name and contact information of the grantor and description of an open or imminent grant application process in which ProgCode may participate.
  3. Grant researcher/writer must be qualified to counsel and advise ProgCode regarding the identified grants.
  4. Directors will report to the community with all relevant information and timely schedule community meetings in which all ProgCode members may participate to discuss ideas, questions, and concerns regarding the information obtained by the grant researcher/writer.

The requirements of Issues #198 and #236 are applicable, as follows:

Proposals seeking consent for implementation of budget requests and/or change process should not contradict ProgCode core objective and should pass this four-pronged test when considered by operations:

  1. Is this proposal non-partisan in nature? Yes
  2. Is this proposal aligned with ProgCode's mission of removing the influence of big money in politics? Yes
  3. Does this proposal seek to empower the grassroots by supporting the creation of open source tech? Yes
  4. Is this proposal sponsored or funded by an outside organization? If yes, the source of the funding must be disclosed. No

Plan

  • Community discussion of all elements of this proposal at the Community Operations Meeting scheduled for Monday, July 26, 2021, at 5pm PT | 6pm MT | 7pm CT | 8pm ET | 1am Tuesday BST/GMT.

  • Vote for consent to implement the establishment of a one-time budget of One Thousand and no/100 Dollars ($1,000.00) and to authorize the Board of Directors to spend those funds, as outlined in this proposal.

  • Notify the community of the vote taken by posting a #team-announcement and sharing the video URL in #operations immediately following the vote for consent to proceed, in accordance with ProgCode procedures, allowing additional votes & feedback during the standard 72-hour waiting period before ratifying the vote.

  • If the vote to implement passes, the Directors shall formally accept the offer made by Justin Spees, as outlined in this proposal.

  • Obtain formal written grant information from Justin Spees and each such other source, which shall be disclosed to the ProgCode community as outlined in this proposal.

  • Retain this issue as an open issue for possible amendment or termination of the grant research/writing services relationship at a later date. This pilot initiative may be amended to include any additional proposals, including grant-related budget proposals, which shall be included in the text of this pilot initiative.

  • Commence discussion and drafting of a new, updated ProgCode budget no later than August 2, 2021.

  • Community discussion of all elements of the 2022.05.05 Amendment to this proposal at the Community Operations Meeting scheduled for Monday, May 9, 2022, at 5pm PT | 6pm MT | 7pm CT | 8pm ET | 1am Tuesday BST/GMT.

  • Vote for consent to implement the establishment of a budget of an additional One Thousand and no/100 Dollars ($1,000.00) consistent with the 2022.05.05 Amendment and to authorize the Board of Directors to spend those funds, as outlined in this proposal.

Decision Making

Consent to implement a standard change per the Change Process

Optional Information

Reference link(s)

Community Discussion History

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment