Return to goals.html CVS log | Up to [local] / www |
File: [local] / www / goals.html (download) (as text)
Revision 1.91, Mon May 27 22:55:20 2019 UTC (5 years ago) by bentley
Substantially clean up and modernize HTML markup across openbsd.org. This was done with three purposes in mind: - to reduce the massive amount of inline HTML, to be easier on developers adding actual content - to allow running the HTML validator across the source (doing this found many unintentional mistakes in the present code, including at least a dozen cases of half- or fully-invisible text) - to separate content from presentation, so appearance can be controlled through stylesheets Great care was taken to keep all pages, even very old ones, looking the same, give or take a few pixels of whitespace. Much review, critique, and improvement from tj@ |
<!doctype html> <html lang=en> <meta charset=utf-8> <title>OpenBSD: Project Goals</title> <meta name="viewport" content="width=device-width, initial-scale=1"> <link rel="stylesheet" type="text/css" href="openbsd.css"> <link rel="canonical" href="https://www.openbsd.org/goals.html"> <style> h2 { color: var(--red); } </style> <h2 id=OpenBSD> <a href="index.html"> <i>Open</i><b>BSD</b></a> Project Goals </h2> <hr> <p> Obviously, each developer working on OpenBSD has their own aims and priorities, but it is possible to classify the goals we all share: <ul> <li>Provide the best development platform possible. <a href="anoncvs.html"> Provide full source access to developers and users, including the ability to look at CVS tree changes directly</a>. Users can even look at our source tree and changes <a href="https://cvsweb.openbsd.org/cgi-bin/cvsweb">directly on the web!</a> <p> <li>Integrate good code from any source with <a href="policy.html">acceptable licenses</a>. ISC or Berkeley style licences are preferred, the GPL is not acceptable when adding new code, NDAs are never acceptable. We want to make available source code that anyone can use for ANY PURPOSE, with no restrictions. <strong>We strive to make our software robust and secure, and encourage companies to use whichever pieces they want to.</strong> There are commercial spin-offs of OpenBSD. <p> <li>Pay attention to <a href="security.html">security problems and fix them before anyone else does</a>. (Try to be the #1 most secure operating system.) <p> <li><a href="crypto.html">Greater integration of cryptographic software.</a> OpenBSD is developed and released from Canada and due to Canadian law it is legal to export crypto to the world (as <a href="http://www.efc.ca/pages/doc/crypto-export.html"> researched by a Canadian individual</a> and as <a href="https://web.archive.org/web/20180128032722/http://axion.physics.ubc.ca/ECL.html"> documented in the Export Control list of Canada</a>). <p> <li>Track and implement standards (ANSI, POSIX, parts of X/Open, etc.) <p> <li>Work towards a very machine independent source tree. <a href="plat.html">Support as many different systems and hardware as feasible.</a> <p> <li>Be as politics-free as possible; solutions should be decided on the basis of technical merit. <p> <li>Focus on being developer-oriented in all senses, including holding developer-only events called <a href="hackathons.html">hackathons</a>. <p> <li>Do not let serious problems sit unsolved. <p> <li>Make a release approximately every six months. </ul> <h2 id=funding>Project Funding</h2> See our <a href="donations.html">Donations Page</a>. <h2>Where do our developers live?</h2> This map approximates where our developers live. We will attempt to update it occasionally, but please don't count on that. <p> <img src="images/map.jpg" height=508 width=950 alt="World map" style="margin: auto">