doc: add funding goals

Signed-off-by: Michael Dawson <midawson@redhat.com>

Nodejs-Funding-Sources.md

@@ -6,6 +6,69 @@ in order to to accept sponsorships.
 The funds are to be used for specific efforts as decided by the TSC and
 documented on this page.
 
+## Funding Goals
+
+The main funding goals for the project include:
+* Security Lead
+* CI stability improvments
+* Project health and collaboration
+
+These goals are as documented in the sections which follow and will
+be documented in GitHub sponsors and Open Colletive pages.
+
+### Security Lead
+
+**Target:** 300,000 US
+
+**Description:** For the past two years the OSSF has funded a security
+lead. This has enabled the project to improve its turn around time for fixing
+vulnerabilities, delivering security releases, making the security release
+process more efficient through automation and reinvigoratnge the project's
+security team.  The reinvigorated security team has mad progress by
+defining the threat model for Node.js, tracking progress against the
+OpenSSF scorecard, and more.
+
+The urgency and fixed deadlines that are often associated with security issues
+are a poor fit for volunteers. Having a security resource whoes job it is to
+work on these issues not only results in faster resolution of security issues,
+but it also avoids burn out of volunteers who might try to squeeze in
+urgent issues along with their regular job.
+
+### CI stability improvments
+
+**Target:** 60,000 US
+
+** Description:** Progress of the project has been impacted by flaky tests over
+a number of years, making it the top pain point for the project contributors.
+The project needs a dedicated resource who will:
+* lead a test reliability strategic initiative, rallying and supporting
+  contributors who work to reduce flaky tests. This might include running
+  regular test team meetings, documentation, tools, or whatever strategy
+  works to achieve more than they can do on their own
+* build tools and improve automation that allows
+  the project to effectively manage flaky tests to reduce their impact on the CI
+* Investigate and fix existing tests being marked as flaky in the status files
+
+### Project health and collaboration
+
+**Target:** 20,000US
+
+**Description:** Funds to be used to support general project health
+and collaboration.
+
+## Sponsor promotion
+
+It is important that we promote non-monetary sponsors at least as well as
+monetary sponsors. We may have limited ability to do that through Open
+Colletive and GitHub sponsors so we should avoid providing links to those
+on the Nodejs.org website or Node.js README.md until we figure out
+how to do that.
+
+We also want to make sure that the message is that we generally prefer
+people to contribute to the project with people versus a monetary sponsorship
+and the ability to make monetary contributions is to cover cases where
+that is not possible.
+
 ## Account details
 
 The accounts are manged by the TSC. The user ids and passwords