Practices in Open Source Software Crowd-funding

Last modified by Administrator on 2018.04.23 at 13:01:06 PDT

Those crowd-funding projects that meet OSI requirements will be able to display the OSI Keyhole Logo and identify themselves as a "Project Developed with an OSI Approved License."

Requirements:

  • If the crowd-funding project is related to an existing software development effort (were source code already exists), the crowd-funded project page must provide a link to that software's publicly accessible source code repository (e.g. GitHub, Sourceforge, self-hosted, etc.).
    • The name of the crowd-funded project must be identical to the name of the project name for the source code repository.
    • The root directory of the named project repository / project site must contain a file named "LICENSE.txt" that includes an OSI Approved License and language specific to the copyright holders.
    • The LICENSE.txt file must include the name of the crowd-funded project in the language of the OSI Approved License (e.g. copyright holders).
  • If the project has not yet begun actual development, the complete text, including the project's name (copyright holder), of an OSI Approved License must be included on the crowd-funding site. For example:
        The MIT License (MIT)
        Copyright (c) <year> <copyright holders>
        Permission is hereby granted, free of charge, to any person...
  • The crowd-funded project must include an OSI Approved License in the first release / distribution of the software.

Important: If any of these requirements are not met, the project may not use either the OSI Approved License label nor the OSI Approved License badge. The OSI may revoke the use of the OSI Approved License label and the OSI Approved License badge at any time for any reason deemed relevant by the OSI Board of Directors.

Possible additional opportunities:

  • Crowd-funding projects are run as OSI Fiscal Sponsorships so that the OSI can guarantee funds are used as described. This would give the projects credibility while giving the contributors security that the projects are legitimate. The contributions would then be tax deductible. This would also provide the OSI with a small revenue stream to administer the service.
  • Provide OSI Affiliate Membership for projects.
  • Develop /cultivate open source best practices (think Mautic and our Open-by-rule discussions).
  • Through Affiliate Membership provide additional resources (Bluehost hosting for projects).
Tags:
Created by Patrick Masson on 2015.01.13 at 12:55:45 PST
    

Submit feedback regarding this wiki to webmaster@opensource.org

This wiki is licensed under a Creative Commons 2.0 license
XWiki Enterprise 7.4.2 - Documentation