LogoLogo
  • Documentation
  • Resources
  • welcome & introduction to osc
    • Welcome to Open Source Collective Docs
    • What is Fiscal Hosting?
    • Our Services & Benefits
    • Fees
    • Terms of Fiscal Sponsorship
  • Interested in Joining OSC?
    • Is OSC Right For My Project?
    • Eligibility Requirements
    • Moving to OSC from Another Fiscal Sponsor
  • Ready To Apply?
    • GitHub Verification
    • Manual Verification
  • For Donors: Companies, Organizations, and Individuals
    • Companies and Organizations
    • Individuals
    • How to Donate
    • Why Projects Use Open Source Collective for Donations
    • Understanding the Types of Funds we Handle
    • Refund Requests
  • for hosted member projects
    • Your Project Was Just Accepted! Now What?
    • Spending Money & Getting Paid
      • Invoices vs. Reimbursements
      • Expense Policies and Limitations
      • Tax & Accounting
      • Expenses Marked as "Incomplete" or otherwise have not been paid
      • Classifying Awards or Gifts
    • Managing Project Funds
      • Handling Donation Refunds: What Projects Need to Know
      • I Was Expecting Money, Where Is It?
      • Reviewing Expenses as an Admin
      • Giving to Other Open Source Projects
      • Using Fiverr, Upwork, or Ko-fi
    • Leaving Open Source Collective
    • Signing and Entering Into Legal Contracts
    • Conference Policy
    • Employment, Payroll, and Benefits
    • Trademarks & IP
    • Domain Transfers and Registration
    • Governance and Mediation
  • Campaigns and Partnerships
    • Google Summer of Code
    • Google Season of Docs
    • GitHub Sponsors
    • Polar.sh
    • Drips
    • Other Payment Platforms
  • About OSC
    • Who and What is OSC?
    • OSC's Broader Work
    • Official Documents & Tax ID
    • Logo & Brand Assets
    • Contact Us
Powered by GitBook
On this page
  • Signing Contracts and Entering Into Legal Agreements
  • For Admins of Hosted Member Projects
  • For Financial Contributors & Sponsors
  • There Are Instances Where We Cannot Sign for You
  1. for hosted member projects

Signing and Entering Into Legal Contracts

How Open Source Collective handles contracts and legal agreements

PreviousLeaving Open Source CollectiveNextConference Policy

Last updated 3 days ago

Signing Contracts and Entering Into Legal Agreements

As the legal representative, Open Source Collective (OSC) will need to review, and likely sign, any agreement for or on behalf of the projects we host.

For Admins of Hosted Member Projects

Open Source Collective will legally be the organization entering into the contract and will be the signer on behalf of your project. Please remind the preparer to draft the contract with Open Source Collective as the signatory.

OSC before entering into any contract and we will discuss the details with you and review/amend/sign on behalf of your project.

For Financial Contributors & Sponsors

OSC is the legal and financial home of our hosted member projects. If you would like to support a project or collective on behalf of your company we can:

  • Register as a vendor to your organization, issue invoices, and manage payments on your behalf.

  • Provide facilities to manage your financial contributions over the course of the year, like with , that can be used to contribute to open source projects.

  • Issue template agreements for general or event-specific sponsorship.

There Are Instances Where We Cannot Sign for You

For example, the Apple Developer Program. Unfortunately we can not offer this to projects. Apple's agreement would be between Apple and OSC. If there was an infraction by one project, it would impact all of the projects under OSC's Apple agreement.

Contact
Funds