So in the last few months, GOAT has accepted funding for various small projects (see a list here) from booth reimbursements to major projects like the Community of Companies. I recently requested GOAT (and NMCC, GOATs fiscal sponsor) to accept funding on behalf of Our Sci for a collaboration with UBC / LiteFarm and run that through our Open Collective for transparency and ease of reimbursement.
As the person who is running the aforementioned funding through GOAT but who also has administrative access to GOATs Open Collective, the potential for conflicts of interest is clear.
This prompted me and @julietnpn both review two things:
- who has the opportunity to use GOAT as a fiscal sponsor (ieā¦ shouldnāt just be me because I close to this stuff) and
- what are the processes for expense approvals (to make sure weāre managing funds without stealing stuff).
So we did a few things:
- We added language on goatech.org describing the option to provide financial hosting so others can also do this.
- We created a written policy of how one can do that, and the details of any engagement are decided. Itās intentionally broad as projects can vary a lot and we need discretion.
- We updated the āPoliciesā page in Open Collective to link to the aforementioned document, and noted that an additional approval for expenses is required if that person is also an admin (ieā¦ admins canāt self-approve alone an expense.
Lastly - Iām posting here and on Element to ask for feedback from the community on the above and also to communicate the option of fiscal hosting through GOAT NMCC when and where appropriate.
We thought weād offer a 5 day comment period (till March 10) here before moving forward on the current Our Sci / UBC proposal. If needed we could extend and have a meeting to discuss if the conversation requires it. Itās short because of the funding turnaround needed on this particular project is fairly quick.
So please ā post any comments, questions, concerns here!
3 Likes
This is a great idea!
Could it be required to add a description of greater length to the Open Collective projectās āAboutā section, with relevant links etc? I eventually pieced together that āOpen Ag Tech Enterpriseā in the project title was roughly the same as the āCommunity of Companiesā you mentioned above, and that the āCommunity of Organizationsā referred to in the GitLab issue for the UBC/LiteFarm collab is also the same ā is that correct? ā but it took a while getting there. And btw, thatās a really awesome project! I love the new conventions wiki, too, first Iām seeing any of this and Iām so glad itās able to move forward. Huzzah!! 
Beyond the approval process, I think fellow GOATs would get a lot of value from hearing about stuff like this, and in exchange for fiscal hosting, it seems like a small price to ask for a decent overview with the most pertinent info and helpful links for where to learn more. Specifically links to the source code and docs (eventually, where relevant) would be a nice requirement, too, since we are GOAT. A good opportunity to show off the material results of the funding.
I put some comments on the policy document there, I hope they make sense.
2 Likes
Good point - I think if weāre really going to invest in Open Collective as a tool for transparency, we need to ensure that documentation is reflected there. Iāll update the about pages with more information and key links on the existing ones, and then if we create this new proposed one there too.
Yeah, excited about the conventions work, weāre hopefully going to build out our first real connection to LiteFarm and Cool Farm Tool (FINALLY) in the next few months. Rose and @OctavioDuarte have put a lot of work into it, and weāre feeling good about it.
2 Likes
Hi GOATy friends:
I like the SOP doc, especially the āwhat to doā, and I like the idea of GOAT acting as facilitator and enabler for money to ethically flow into worthy and aligned projects. In the interest of clarity and noting that if someone can explain a thing to me they can explain it to anybody, I have a couple questions!
Is the idea that people or companies that become hosted/sponsored are publicly saying they are part of GOAT from a technology and philosophy standpoint, and they want and are agreeing to financial transparency, and GOAT is saying āyou can be included in the nonprofit umbrella provided by NMCC and we will do things in Open Collective to make sure your project is transparentā?
Iām super out of the loop, sorry: does GOAT itself exist as a legal entity? Wondering about how the relationship between GOAT the Community and extra-human beings like LLCās, corporations, and cooperatives plays into the relationship with NMCC which I think as fiscal sponsor has some kind of legal responsibility for the management of money it passes along, and that is why it needs a cut.
I added some possibly trauma-informed suggestions to the doc (ok to reject if not useful) as I have been part of a nonprofit that took on fiscal sponsorships in totally good faith which ended up being problematic and distracted precious energy from our mission, and part of pass-through funding things that likewise didnāt go well and those were likewise way too extra. Of course the ones that worked out were wonderful! 
2 Likes
Wow, really great questions @laurieWayne !
Goat itself doesnāt exist as a legal entity.
Iām not sure if we need to specify any explicit philosophical or organizational commitments at this juncture. We donāt want to introduce additional complexity / overhead until its really required. At the moment it is unclear how widely this service is needed or will be utilized. With that said, I think that for the time being, folks engaging will inherently be values aligned because its a service weāre offering to the community specifically. But yes, theyād be agreeing to financial transparency. And we (GOAT) would work with the organizations involved in the project being financially managed on GOATās open collective infrastructure to define a protocol appropriate for that project.
I see this as an evolving process that will be refined as we work through it, with the Our-Sci & UBC collaboration as our pilot. So while there is 5 days comment period on this specific contract, the comment and refinement period for this service broadly should be ongoing.
Thanks for the doc suggestions - I donāt have the answer to those, but Iāve tagged the necessary GOATs for review. 
1 Like
Yes, good questions. One thing that GOSH did is they set a clear line for āinsideā and āoutsideā the community - things like āyouāve been to a conferenceā or āyouāve been active for >X years on the forumāā¦ that kind of thing. Thatās an interesting and non-organizational way to draw a boundary we could use too.
But overall I agree with Juliet - letās let our function be driven by need and demand, and keep it as simple as possible until the community screams otherwise.