Mostly writing it down for myself to have a clear (and shareable) TODO list.
Our "*nix-like" toolkit will most likely be provided by ToyBox (public domain equivalent license) and our remote terminal implementation of choice is openssh-portable (3-clause BSD license or freer) ported by Microsoft heroes and tuned for MinGW by ourselves. The latter uses its own POSIX-on-Windows compatibility layer; for the needs of the former, our intent is to complement MinGW (and the underlying Microsoft CRTs) in the least invasive way possible.
Subsystems and components intended for general use (public domain)
These components will be consumed by userspace, user-facing, mostly GUI applications. While incorporation of code under non-PD permissive licenses should generally be OK during development/porting of such packages, the lodestar goal for user-facing apps should be "original license for the application package, OS or public domain all the way down". (A rule of thumb for exceptions is that dependencies qualify for an exception if they are extremely hard to overlook — e.g. "dependency D1 is the original application framework" (Qt, Electron…) or "dependency D2 is the rendering API provider" (Mesa, ANGLE…).)
win32iocompat (the OpenSSH-on-Windows porting layer)
Components aware of the win32iocompat layer (alternative names: win32compat, posix_compat) are intended for development and system administration tools. They must be available under a 3-clause BSD or a freer license.
Mostly writing it down for myself to have a clear (and shareable) TODO list.
Our "*nix-like" toolkit will most likely be provided by ToyBox (public domain equivalent license) and our remote terminal implementation of choice is openssh-portable (3-clause BSD license or freer) ported by Microsoft heroes and tuned for MinGW by ourselves. The latter uses its own POSIX-on-Windows compatibility layer; for the needs of the former, our intent is to complement MinGW (and the underlying Microsoft CRTs) in the least invasive way possible.
Subsystems and components intended for general use (public domain)
These components will be consumed by userspace, user-facing, mostly GUI applications. While incorporation of code under non-PD permissive licenses should generally be OK during development/porting of such packages, the lodestar goal for user-facing apps should be "original license for the application package, OS or public domain all the way down". (A rule of thumb for exceptions is that dependencies qualify for an exception if they are extremely hard to overlook — e.g. "dependency D1 is the original application framework" (Qt, Electron…) or "dependency D2 is the rendering API provider" (Mesa, ANGLE…).)
pwd.handgrp.h— provided bylibwuserslibfatctl*xattr()API — provided bylibxxxattrlibchoreo*chown*()APIs — provided bylibownerssys/mman.h— provided bylibmemmapws2fwdonly adds one-line forwarding headers).stderroutput (short term), come up with something like OSX Console (long term) with most important notifications promoted to Event Log./proc(for debugging tools) — MOREINFO provide on a per-process basis, most likely with embedded named pipe servers.win32iocompat(the OpenSSH-on-Windows porting layer)Components aware of the
win32iocompatlayer (alternative names:win32compat,posix_compat) are intended for development and system administration tools. They must be available under a 3-clause BSD or a freer license.termios.h) — currently present inwin32iocompat; troubleshoot and possibly extract. (Check the box when the default incoming session is stable.)