Open Source License

The License Review Process

The Goal Of The OSI License Review Process Is To Ensure That Licenses And Software Labeled As "Open Source" Conform To Existing Community Norms And Expectations. For That Reason, All Licenses Must Go Through A Public Review Process Described Below. The OSI Board Is Happy To Consult With Entities In Advance To Help Them Navigate The Process And Improve Their License, But Formal Approval Requires Going Through License-Review.

Purpose Of The Process

Ensure Approved Licenses Conform To The Open Source Definition And Provide Software Freedom

Identify Appropriate License Proliferation Category

Discourage Vanity And Duplicative Licenses

Ensure A Thorough, Transparent And Timely Review (E.G. Within 60 Days)

Decision Process

The OSI Has Adopted The Guidelines Below, Which We Aim To Follow When Reviewing Licenses, To Ensure That A License Will Be Approved Only If It Conforms To The Open Source Definition And Provides Software Freedom.

"Decision Date" For A License Normally Means (A) 60 Days After A License Is Initially Submitted To The License-Review List For Review, And (B) 30 Days After Submission Of A Revised Version Of A License That Was Previously Submitted For Review. A License Is Considered To Be Submitted For Review If It Follows The Process Set Forth At Https://Opensource.Org/Approval. While We Will Try Our Best To Adhere Strictly To This 60/30 Day Decision Date Definition, Circumstances May Require Us To Extend The Decision Date Further.

No Later Than The Next Available Board Meeting After The Decision Date, The OSI Will Select One Of Four Possible Decisions:

Approve If, After Taking Into Consideration Community Discussion, The OSI Determines That The License Conforms To The Open Source Definition And Guarantees Software Freedom. A License May Be Approved On The Condition That A Change Be Made, But In General A License Requiring Changes Will Have To Be Resubmitted.

Eject If (A) The OSI Determines That The License Cannot Practically Be Remedied To Adequately Guarantee Software Freedom, Or (B) There Is Sufficient Consensus Emerging From Community Discussion That The License Should Be Rejected For Substantive Reasons, Or (C) The License Is Problematic For Nonsubstantive Reasons (For Example, It Is Poorly Drafted Or Significantly Duplicative Of One Or More Existing OSI-Approved Licenses).

Withhold Approval, If (A) The OSI Determines That Approval Would Require Reworking The License And (B) The License Submitter Appears Willing And Able To Revise The License Constructively