[License-review] Submission of Orivex Syscall Note License (OSN-1.0) for OSI Approval
Righteousness
karuman2013 at gmail.com
Mon Oct 20 13:09:03 UTC 2025
Dear Open Source Initiative License Review Committee,
I am submitting the Orivex Syscall Note License (OSN-1.0) for your
consideration for OSI approval.
Background:
Orivex is an operating system currently under active development. OSN-1.0
is a permissive license specifically designed for Orivex’s kernel-facing
components, including kernel headers, syscall interface definitions,
reference ABI documentation, and related API files. This license is
intended to enable Orivex to be released as open source in the future.
Why a New License is Necessary:
Existing OSI-approved licenses, such as MIT, BSD, or Apache 2.0, provide
general-purpose permissive licensing but do not explicitly address kernel-
and syscall-level artifacts. OSN-1.0 fills this gap by:
- Preserving attribution and provenance specifically for kernel interfaces
and ABI contracts.
- Providing guidance for ABI and syscall interface compatibility without
imposing legal obligations.
- Explicitly separating trademark rights from copyright and patent grants.
- Clarifying contributor patent grants and termination conditions related
to patent litigation.
Comparison to Similar OSI Licenses:
- MIT/BSD: Similar in permissiveness and simplicity, but do not provide
guidance on syscall/ABI traceability or contributor patent grant clarity.
- Apache 2.0: Includes patent grants and some attribution requirements, but
is heavier and not tailored for kernel-facing artifacts or syscall-specific
documentation.
OSN-1.0 balances permissiveness, clarity, and lightweight design, while
providing explicit protections and guidance for kernel interface
development.
Open Source Definition Compliance:
OSN-1.0 has been designed to satisfy all ten criteria of the Open Source
Definition (OSD), including:
- Free redistribution
- Availability of source code
- Permission to create derivative works
- No discrimination against persons, groups, or fields of endeavor
- Technology-neutral terms
- Clear redistribution and license grant requirements
Additional Information:
- Copyright (c) 2025 Kartik
- SPDX Identifier: Orivex-syscall-note
- Governing Law: India
I believe OSN-1.0 provides a clear, permissive license suitable for
projects requiring kernel- or syscall-level interfaces while remaining
fully OSD-compliant. I would be happy to provide any additional
information, clarifications, or documentation needed to facilitate your
review.
Thank you for your time and consideration.
Best regards,
Kartik
karuman2013 at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensource.org/pipermail/license-review_lists.opensource.org/attachments/20251020/989c9f94/attachment-0001.htm>
-------------- next part --------------
SPDX-License-Identifier: Orivex-syscall-note
ORIVEX SYSCALL NOTE LICENSE (OSN-1.0)
Copyright (c) 2025 Kartik
Preamble
--------
The Orivex Syscall Note License (OSN-1.0) is a permissive open-source license tailored for
kernel-facing artifacts such as kernel headers, syscall interface definitions, reference ABI
documentation, and related API files (collectively, the "Software"). OSN-1.0 seeks to:
(a) provide broad, unencumbered rights to use, modify, and redistribute the Software;
(b) preserve attribution and provenance of kernel interface definitions and ABI contracts;
(c) encourage upstream compatibility and traceability of changes to syscall interfaces;
(d) protect Orivex trademarks and identity by separating trademark rights from copyright
and patent grants; and
(e) clarify contributor patent grants and termination on patent litigation.
1. Definitions
--------------
In this License:
1.1 "You" (or "Your") means any individual or legal entity exercising Rights under this
License.
1.2 "Licensor" means the copyright holder(s) identified at the top of this document or
any entity that subsequently holds copyright in the Software and distributes it under
OSN-1.0.
1.3 "Contributor" means any individual or legal entity that submits Contributions to the
Software.
1.4 "Contribution" means any original work of authorship, including modifications and
additions, submitted to the Software and intentionally contributed by You to the
Licensor for inclusion in the Software.
1.5 "Derivative Work" has the meaning given by applicable law, and includes works that
incorporate or are based upon the Software.
1.6 "Distribution" means any transfer, conveyance, sale, sublicense, lease, or public
offering of the Software or derivative works thereof, in source or binary/object form.
1.7 "Notice File" means a file named SYSCALL-LICENSE.md or NOTICE, or other similarly
prominent file, used to communicate attribution, license terms, or other required
notices to recipients of the Software.
1.8 "Binary Form" means object code or any form other than readable source code.
1.9 "Source Form" means the preferred form for making modifications, including but not
limited to original source code, documentation source, and build scripts.
2. Grant of Copyright License
-----------------------------
Subject to the terms and conditions of this License, the Licensor hereby grants You a
worldwide, royalty-free, non-exclusive, perpetual, irrevocable copyright license to:
2.1 Reproduce and prepare Derivative Works of the Software;
2.2 Distribute, sublicense, and publicly display the Software in Source Form and Binary Form;
2.3 Perform and otherwise use the Software for any purpose, including commercial use;
2.4 Permit third parties to exercise any of the foregoing rights.
3. Patent License
-----------------
3.1 Patent Grant by Licensor. Subject to the terms of this License, the Licensor grants
You a worldwide, royalty-free, non-exclusive, perpetual patent license under
Licensor-owned patents to make, use, sell, offer to sell, import, and otherwise
distribute the Software, but only to the extent such patent claims are necessarily
infringed by the Software as delivered by the Licensor.
3.2 Patent Grant by Contributor. By making a Contribution, each Contributor hereby grants
You a worldwide, royalty-free, non-exclusive, perpetual patent license under any
patent claims that are necessarily infringed by their Contribution alone or by the
Contribution when combined with the Software submitted to the Licensor.
3.3 Termination for Patent Litigation. If You (or any entity controlled by You) institutes
or causes to be instituted any patent litigation (including a cross-claim or counterclaim)
against any party alleging that the Software or a Contribution infringes a patent,
then any patent licenses granted to You under Sections 3.1 or 3.2 for the Software
shall terminate as to the party to whom such license was granted.
4. Redistribution: Source and Binary Requirements
------------------------------------------------
Redistributions of the Software, in Source or Binary Form, must meet the following:
4.1 License Copy. Redistributions must include a complete, unmodified copy of this
OSN-1.0 License text or a machine-readable reference to it (for Binary Form),
and the SPDX identifier where feasible.
4.2 Copyright and Notices. Redistributions must retain, in all source files and in any
distributed NOTICE or SYSCALL-LICENSE.md file, all copyright, patent, and attribution
notices that appear in the Software.
4.3 Prominent Attribution Note. Redistributions must include in a prominent location (for
example a top-level README, NOTICE, or SYSCALL-LICENSE.md) the statement:
"This distribution includes Orivex syscall interfaces (OSN-1.0). See SYSCALL-LICENSE.md
or NOTICE for details."
4.4 SYSCALL-CHANGES.md. If You modify files covered by the Software, You must include a
SYSCALL-CHANGES.md documenting the nature of changes (short summary, author, and date)
and distribute it alongside the modified files. This requirement is for provenance and
traceability and does not otherwise limit Your rights to modify or distribute.
4.5 Binary Form. For Binary Form redistributions, You must reproduce the information
required by Sections 4.1–4.4 in a NOTICE or equivalent documentation distributed with
the Binary (e.g., in a top-level directory, installer, or package metadata).
4.6 Sublicensing. You may grant sublicenses to downstream recipients, provided sublicenses
preserve the requirements of this License with respect to the portions of the Software
covered by OSN-1.0.
5. Contribution Policy and Developer Agreement
----------------------------------------------
5.1 By submitting a Contribution to the Software, You represent that You have the right to
grant the rights described in this License and that Your Contribution does not violate
any third-party rights.
5.2 Each Contributor grants the Licensor and recipients of the Software the licenses
described in Sections 2 and 3 for their Contribution.
5.3 Optionally, the Licensor may provide a Contributor License Agreement (CLA) or Developer
Agreement for signature; signing such an agreement is not mandatory to contribute but
may be required by the project for administrative or corporate compliance reasons.
5.4 The Licensor may, at its discretion, refuse to accept contributions that are encumbered
by third-party license terms incompatible with OSN-1.0.
6. Compatibility and Stability Guidance
---------------------------------------
6.1 Compatibility Encouragement. The Licensor strongly encourages contributors and downstream
redistributors to preserve ABI and syscall interface compatibility where possible.
6.2 Deprecation and Breaking Changes. Where a change breaks compatibility, the party making
the change should document the change, provide an upstream notice, and, where reasonably
practicable, offer a deprecation period sufficient to allow downstream projects to adapt.
6.3 Not a License Obligation. The guidance in this Section 6 is non-binding and intended
to encourage cooperative development; it does not create legal obligations beyond those
expressly stated in other sections of this License.
7. Trademarks, Name & Logos
---------------------------
7.1 No Trademark Grant. This License does not grant permission to use trade names, trademarks,
service marks, logos, or product names of the Licensor, except as required solely to
identify the origin of the Software in notices as required by Section 4.3.
7.2 Referencing the Orivex Name. You may refer to the Software as "Orivex syscall interfaces"
for identification and compatibility descriptions, provided such references do not imply
endorsement by the Orivex project or use of Orivex trademarks beyond the limited attribution
permitted by Section 4.3.
7.3 Separate Trademark Policies. The Licensor may publish separate trademark usage guidelines;
compliance with such guidelines is required to make use of Orivex trademarks beyond the
attribution described above.
8. Disclaimer of Warranty
-------------------------
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
NON-INFRINGEMENT. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE SOFTWARE IS WITH YOU.
9. Limitation of Liability
--------------------------
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL THE LICENSOR OR ANY
CONTRIBUTOR BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, PUNITIVE, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION), HOWEVER CAUSED AND ON
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
OR OTHERWISE), ARISING IN ANY WAY OUT OF THE USE OF THE SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
10. Indemnity
-------------
Unless otherwise agreed in a separate written agreement, You agree (to the extent permitted
by applicable law) to indemnify, defend and hold harmless the Licensor and its Contributors
from and against any claim, liability, loss, damage, or expense (including reasonable legal
fees) arising out of Your modification, distribution, or use of the Software, or any violation
of this License by You.
11. Termination
---------------
11.1 Automatic Termination. Your rights under this License will terminate automatically if You
fail to comply with any of its terms and fail to cure such non-compliance within thirty
(30) days of receiving written notice from the Licensor; provided that termination of Your
rights will not terminate rights that have already been granted by You to third parties
if those third parties received the Software lawfully and in compliance with this License.
11.2 Effect of Termination. Upon termination, You must cease all distribution of the Software
that relies on rights under this License, except that You may continue to use and distribute
any portions of the Software that were received under a separate license or prior lawful grant.
11.3 Survival. Provisions that by their nature survive termination shall survive, including
Sections 3 (Patent License, to the extent it survived by applicable law), 8 (Disclaimer
of Warranty), 9 (Limitation of Liability), 10 (Indemnity), 11 (Termination), 12 (Severability),
and 13 (Governing Law & Dispute Resolution).
12. Export Controls & Applicable Law
-----------------------------------
12.1 Export Compliance. You are solely responsible for complying with all applicable export
and import laws and regulations. The Licensor makes no representation that the Software
may be exported or used under any particular jurisdiction.
12.2 Governing Law & Jurisdiction. This License shall be governed by and construed in accordance
with the laws of India without regard to its conflict of law principles. Any disputes arising
out of or relating to this License shall be subject to the exclusive jurisdiction of the
courts located in New Delhi, India.
13. Severability
---------------
If any provision of this License is held to be invalid, illegal, or unenforceable under
applicable law, such provision shall be reformed only to the extent necessary to make it valid,
legal, and enforceable, and the remaining provisions shall remain in full force and effect.
14. Interpretation & Entire Agreement
-------------------------------------
This License constitutes the entire agreement between the parties with respect to the subject
matter hereof and supersedes any prior or contemporaneous agreements, understandings, or
arrangements. Headings are for convenience only and shall not affect interpretation.
15. How to Apply This License
-----------------------------
To apply this license to your work, attach the following copyright and license header to each
source file or include it in a top-level license file; keep the SPDX identifier if possible.
Suggested source-file header:
/*
<OPTIONAL MESSAGE>
Copyright (C) <YEAR> <COPYRIGHT HOLDER>
<PROJECT NAME> is distributed under the Orivex Syscall Note License (OSN),
version <VERSION> or any later version at your option.
The software is provided as-is, without any guarantees or warranties of any kind.
See SYSCALL-LICENSE.md or NOTICE for the full license terms.
*/
16. Recommended Top-Level Files
-------------------------------
It is recommended that distributions include the following top-level files:
16.1 SYSCALL-LICENSE.md -- Full license text or a pointer to this OSN-1.0 text.
16.2 NOTICE or README -- Attribution statement required by Section 4.3.
16.3 SYSCALL-CHANGES.md -- Record of notable modifications to syscall/ABI files.
16.4 CONTRIBUTORS (optional) -- List of significant contributors and their affiliations.
Appendix A — Suggested NOTICE / SYSCALL-LICENSE.md Template
------------------------------------------------------------
This distribution contains Orivex syscall interfaces licensed under the Orivex Syscall Note
License (OSN-1.0). See the file SYSCALL-LICENSE.md for the full license text.
Copyright (c) 2025 Kartik
This NOTICE file lists notices and attributions required by OSN-1.0:
- "Orivex syscall interfaces (OSN-1.0) — see SYSCALL-LICENSE.md"
- Any additional notices retained from upstream sources.
Appendix B — Suggested SYSCALL-CHANGES.md Template
--------------------------------------------------
File: <relative-path-to-file>
Author: <name / organization>
Date: <YYYY-MM-DD>
Summary:
- <Short description of changes; e.g., "Added new socket syscall number", "Renamed struct foo to bar">
Impact:
- <Backward-compatibility impact (none / deprecation / breaking)>
Final Notes
-----------
* This license is intended to be permissive and broadly compatible with open-source ecosystems,
while providing clear attribution and contributor patent protections.
* This document is a legal instrument. You may wish to have counsel review this text before
formal adoption for a major project or before making formal submissions to standards bodies
or the Open Source Initiative.
* If you want, I can:
- produce a one-page "license summary" for your README,
- prepare an OSI submission cover letter draft explaining how OSN-1.0 differs from MIT/BSD/Apache,
- or generate ready-to-drop SYSCALL-LICENSE.md, NOTICE, and SYSCALL-CHANGES.md files.
END OF LICENSE
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SYSCALL-LICENSE.md
Type: application/octet-stream
Size: 1653 bytes
Desc: not available
URL: <http://lists.opensource.org/pipermail/license-review_lists.opensource.org/attachments/20251020/989c9f94/attachment-0001.a>
More information about the License-review
mailing list