I think this looks great! -Brent > On Feb 23, 2020, at 5:02 PM, Maciej Stachowiak <[email protected]> wrote: > > > V2, with stronger privacy language. > > > project-new.html > 1111 WebKit is an open source Web content engine for browsers and other > applications. > 1212</p></blockquote> > 1313<p><img src="/wp-content/themes/webkit/images/webkit.svg" alt="The WebKit > Project Logo" class="aligncenter size-full wp-image-4290" width="33%"></p> > 14 <p>We value real-world web compatibility, standards compliance, stability, > performance, security, portability, usability, and relative ease of > understanding and modifying the code (hackability).</p> > 14<p>We value real-world web compatibility, standards compliance, stability, > performance, battery life, security, privacy, portability, usability, and > relative ease of understanding and modifying the code (hackability).</p> > 1515<h2><a name="project-goals"></a>Project Goals</h2> > 1616<h4><a name="web-content-engine"></a>Web Content Engine</h4> > 17 <p>The project’s primary focus is content deployed on the World Wide Web, > using standards-based technologies such as HTML, CSS, JavaScript and the DOM. > However, we also want to make it possible to embed WebKit in other > applications, and to use it as a general-purpose display and interaction > engine.</p> > 17<p>The project’s primary focus is content deployed on the World Wide Web, > using standards-based technologies such as HTML, CSS, JavaScript and DOM. > However, we also want to make it possible to embed WebKit in other > applications, and to use it as a general-purpose display and interaction > engine.</p> > 1818<h4><a name="open-source"></a>Open Source</h4> > 1919<p>WebKit should remain freely usable for both open source and > proprietary applications. To that end, we use BSD-style and LGPL licenses. > Specifically, we aim for licensing compatible with LGPL 2.1+. We do not > currently plan to move to LGPL 3. In addition, we strive to create a > courteous, welcoming environment that feels approachable to newcomers. WebKit > maintains a public IRC chat room and a public mailing list where the ideas of > contributors both new and old are heard and discussed with equal weight.</p> > 2020<h4><a name="compatibility"></a>Compatibility</h4> > > 2424<h4><a name="stability"></a>Stability</h4> > 2525<p>The main WebKit code base should always maintain a high degree of > stability. This means that crashes, hangs and regressions should be dealt > with promptly, rather than letting them pile up.</p> > 2626<h4><a name="performance"></a>Performance</h4> > 27 <p>Maintaining and improving speed and memory use is an important goal. We > never consider performance “good enough”, but strive to constantly improve. > As web content becomes richer and more complex, and as web browsers run on > more limited devices, performance gains continue to have value even if normal > browsing seems fast enough.</p> > 27<p>Maintaining and improving speed and memory use is an important goal. We > never consider performance “good enough”, but strive to constantly improve. > As web content becomes richer and more complex, and as web browsers run on > more limited devices, performance gains continue to have value even if normal > browsing seems fast enough. We consider speed, memory use, responsiveness and > frame rate to be important aspects of performance.</p> > 28<h4><a name="battery-life"></a>Battery Life</h4> > 29<p>In addition to traditional performance metrics, we aim to minimize > power consumption to maximize browsing battery life for portable devices.</p> > 2830<h4><a name="security"></a>Security</h4> > 2931<p>Protecting users from security violations is critical. We fix security > issues promptly to protect users and maintain their trust.</p> > 32<h4><a name="privacy"></a>Privacy</h4> > 33<p>We believe privacy is a human right. WebKit code won't track the user > or otherwise violate their privacy. And we will strive to prevent websites > and other parties from doing so.</p> > 3034<h4><a name="portability"></a>Portability</h4> > 3135<p>The WebKit project seeks to address a variety of needs. We want to > make it reasonable to port WebKit to a variety of desktop, mobile, embedded > and other platforms. We will provide the infrastructure to do this with tight > platform integration, reusing native platform services where appropriate and > providing friendly embedding APIs.</p> > 3236<h4><a name="usability"></a>Usability</h4>
_______________________________________________ webkit-dev mailing list [email protected] https://lists.webkit.org/mailman/listinfo/webkit-dev
