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

📝 Fiscal Sponsorship Agreements [due Jan 17] #219

Merged
merged 13 commits into from
Jan 27, 2025
Merged

📝 Fiscal Sponsorship Agreements [due Jan 17] #219

merged 13 commits into from
Jan 27, 2025

Conversation

ebullient
Copy link
Member

@ebullient ebullient commented Dec 17, 2024

🗳️ Vote progress

This PR defines the agreements and terms for officially transitioning projects and assets to the Foundation.

  1. The Fiscal Sponsorship Agreement is the formal legal contract between the Commonhaus Foundation (“Sponsor”) and a Project’s representatives (“Signatories”). It sets out the legal relationship, roles, and responsibilities for Projects under the Foundation’s fiscal sponsorship.

  2. The Terms and Conditions for Fiscal Sponsorship provides detailed operational guidelines for sponsored Projects. These Terms clarify how Projects are supported, outline financial and administrative processes, and define responsibilities for both the Project and the Sponsor.

  3. The Asset Transfer Agreement governs the transfer of assets (such as funds, trademarks, or other property) from the current owner (the “Assignor”) to the Sponsor as part of the fiscal sponsorship arrangement.

When we have approved these documents, each project will effectively be at the beginning of the On-boarding phase (as described in the Terms and Conditions).

voting group: @commonhaus/cf-egc

Do one of the following:

  • Approve the PR or react with 👍 (:+1:) if it looks good to you
  • Review with Comments or react with 👀 (:eyes:) if you're "ok" with it (it may not be your favorite)
  • If you think it needs discussion or revision
    • Create a review, add your comments and require changes
    • Use the +- button to make a suggestion (instead of just adding a comment).

@ebullient ebullient requested review from a team as code owners December 17, 2024 01:54
@haus-rules-bot haus-rules-bot bot added the notice Notice (review, announcement) label Dec 17, 2024
@ebullient ebullient added the vote/open Vote open label Dec 17, 2024
Copy link

haus-rules-bot bot commented Dec 17, 2024

This vote has been closed by ebullient:

Merging this with the understanding that there will be an additional PR with the resolution of #225


✅ 13 of 15 members of @commonhaus/cf-egc have voted (reaction or review, quorum=2/3).

Reaction Total Team Voting members
approve 8 8 Naros, aalmiray, criccomini, dandreadis, ebullient, evanchooly, marc0der, tristantarrant
ok 5 5 cealsair, cowtowncoder, gavinking, henri-tremblay, kenfinnigan

The following votes were not counted (duplicates):
Naros(👍), aalmiray(👀), criccomini(👀), kenfinnigan(👍), marc0der(👀)

Copy link
Member

@criccomini criccomini left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall, LGTM. I left a few random questions.

@cowtowncoder
Copy link
Contributor

Ok one clarifying question: is the (full) Transfer of Assets meant to be part of on-boarding (actually joining) foundation, or is this more for possible case of current project owner(s) wanting to move on and hand over project to Foundation?

I assume former (given it is not intention of Foundation to manage projects itself)?

So far I have assumed that some aspects would remain for projects to manage.

I guess I am not quite clear on scope of these agreements.

@ebullient
Copy link
Member Author

ebullient commented Dec 19, 2024

Ok one clarifying question: is the (full) Transfer of Assets meant to be part of on-boarding (actually joining) foundation, or is this more for possible case of current project owner(s) wanting to move on and hand over project to Foundation?

I assume former (given it is not intention of Foundation to manage projects itself)?

So far I have assumed that some aspects would remain for projects to manage.

I guess I am not quite clear on scope of these agreements.

Part of on-boarding is discovery and listing of assets. Some things must be transferred, some things could wait. We could decide that some things won't ever, and are better managed for all concerned using some other structure. In all cases, the project will continue to manage itself.

There is a level of transparency and partnership here to figure out what the right (and least disruptive) thing to do is.

@ebullient ebullient force-pushed the hosting branch 2 times, most recently from f65b508 to 552d3f7 Compare January 7, 2025 23:40
@ebullient ebullient changed the title 📝 Fiscal Sponsorship Agreements 📝 Fiscal Sponsorship Agreements [Due Jan 17] Jan 8, 2025
@ebullient ebullient changed the title 📝 Fiscal Sponsorship Agreements [Due Jan 17] 📝 Fiscal Sponsorship Agreements [due Jan 17] Jan 8, 2025
@kenfinnigan
Copy link
Member

I've taken a look at this again, looks good

@criccomini
Copy link
Member

LGTM. Left a few notes and comments, but I'm comfortable.

Copy link
Contributor

@cealsair cealsair left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done with my review. Overall, it looks good to me. I have left a few comments/suggestions. Thanks.

@yrodiere
Copy link
Contributor

Looks like this was due Jan 17 and nobody objected, so... can this get merged?

I need to link to it from another website :)

@ebullient
Copy link
Member Author

Looks like this was due Jan 17 and nobody objected, so... can this get merged?

I need to link to it from another website :)

Need input from @gavinking, @tristantarrant, @maxandersen, and @dandreadis .. I think you know where to find them.

@haus-rules-bot haus-rules-bot bot added the vote/quorum Vote has quorum of electronic responses label Jan 25, 2025
@ebullient ebullient dismissed gavinking’s stale review January 27, 2025 18:23

Will resolve in subsequent PR with result of discussion in #225

@ebullient
Copy link
Member Author

vote::result Merging this with the understanding that there will be an additional PR with the resolution of #225

@haus-rules-bot haus-rules-bot bot added vote/done Vote closed and removed vote/open Vote open labels Jan 27, 2025
@ebullient ebullient merged commit 76838ef into main Jan 27, 2025
2 checks passed
@ebullient ebullient deleted the hosting branch January 27, 2025 18:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
notice Notice (review, announcement) vote/done Vote closed vote/quorum Vote has quorum of electronic responses
Projects
None yet
Development

Successfully merging this pull request may close these issues.