<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Proposal of an open source framework or standards of BSD operating systems<br/>
and software, to increase collaboration and progress between the BSD's<br/>
and BSD software while MidnightBSD and other BSD's can still work independently of each other.<br/>
<br/>
An opensource framework would like how there are different organizations<br/>
and projects that use XMPP, SIP, ePUB, IAX, WebRTC, MQTT, MGCP and CAP.<br/>
Such organizations that govern opensource frameworks include IETF, XMPP foundation,<br/>
Oasis and W3C. It doesn't have to be a strict set of standards, and all BSD's<br/>
don't have to comply perfectly, but can be voluntarily endorsed as applying to a specification.<br/>
<br/>
The point would be to promote progress on different opensource software used by<br/>
MidnightBSD, DragonflyBSD, OpenBSD, NetBSD, FreeBSD, etc while each operating system remains on its own terms.<br/>
<br/>
For instance, OSS implementations are already used. It can get developers<br/>
from all of these operating systems working together, for standardization<br/>
among OSS, Sndio or a BSD implementation of Portaudio. One standard in this<br/>
would be the equivalent of an XEP or RFC of IETF. MidnightBSD can choose<br/>
to take part in one or multiple of these.<br/>
<br/>
Other standards that would be beneficial are HID standards (which many BSD's<br/>
already use or adopting to), compiling tool chains, development utilities,<br/>
build utilities, display servers (Xenocara, Xorg and/or Wayland collaboration)<br/>
implementations, printer drivers, scanner driver standards, Zeroconf implementations.<br/>
<br/>
It can also be for software standards, which are commonly used software with<br/>
FreeBSD. Software would voluntarily verify themselves by those standards, and<br/>
it doesn't all have to be standardized rigidly. Organizations such as ISC<br/>
could collaborate on software standards. There can be multiple standards for<br/>
licenses as well, which are optional, mainly permissive and non-viral.<br/>
<br/>
The best way forward with a standards organization, which can be of multiple<br/>
BSD's or any BSD working as an organization, would be for loose criteria for<br/>
what makes a BSD at its core, and the full operating system doesn't have to be<br/>
fully under those basic standards. The purpose is that it's inclusive of BSD's,<br/>
based on what they're known for. As in IETF or XEP, many standards are optional<br/>
or unofficial, but even the unofficial ones are implemented in a professional<br/>
capacity. It could be run together from many BSD operating systems, or even loosely<br/>
run from several organizations, but the goal would be a loose cohesiveness. Also,<br/>
it would be useful for software that's specifically developed or implemented on different BSD's.<br/>
<br/>
Thank you!</div></div></body></html>