[License-review] Submission of Orivex Syscall Note License (OSN-1.0) for OSI Approval - Revised Submission (Kartik Pawar)

[Rob Landley]

On 10/26/25 10:17, McCoy Smith wrote:
> 4. I don't see what the point is of having a license like this that is 
> restricted to a specific class of software. If you want to attach this 
> license to interfaces, syscalls, and the like, you could just as easily 
> release those components with an MIT or Apache license attached, as the 
> licensed "Software" (or "Work" in Apache) and get essentially the same 
> result. If, for whatever reason you don't like the attribution 
> requirements of MIT or Apache and prefer the attribution requirements in 
> Sec 4, then just write a standard open source grant (like either of 
> those licenses, or others) with this new attribution requirement.

Or use a "public domain equivalent" license like 0BSD which doesn't have 
an attribution requirement. (It's in the github choose-a-license 
pulldown menu for new repositories.)

https://en.wikipedia.org/wiki/Public-domain-equivalent_license

Rob