--===============0346408819==
Content-type: multipart/alternative;
boundary="Apple-Mail=_9462F648-BAE3-4864-B995-AE06A108F753"
--Apple-Mail=_9462F648-BAE3-4864-B995-AE06A108F753
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8
New version, with Oxford comma everywhere. I didn=E2=80=99t add the use =
of =E2=80=9Citself=E2=80=9D because I don=E2=80=99t think the sentence =
is ambiguous as written, given the second clause. And if it is =
ambiguous, =E2=80=9Citself=E2=80=9D would not remove the ambiguity.
Below the diff, there=E2=80=99s the full text of the page as it would =
appear with these diffs applied (though without styling).
project-new.html
1111 WebKit is an open source Web content engine for browsers and other =
applications.
1212
1313
14 We value real-world web compatibility, standards compliance, =
stability, performance, security, portability, usability, and relative =
ease of understanding and modifying the code (hackability).
14We 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).
1515Project Goals
1616Web Content Engine
17 The project=E2=80=99s 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.
17The project=E2=80=99s 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.
1818Open Source
19 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.
19WebKit 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 chat room and a public mailing list =
where the ideas of contributors both new and old are heard and discussed =
with equal weight.
2020Compatibility
2121For users browsing the web, compatibility with their existing =
sites is essential. We strive to maintain and improve compatibility with =
existing web content, sometimes even at the expense of standards. We use =
regression testing to maintain our compatibility gains.
2222Standards Compliance
23 WebKit aims for compliance with relevant web standards, and =
support for new standards In addition to improving compliance, we =
participate in the web standards community to bring new technologies =
into standards, and to make sure new standards are practical to =
implement in our engine. We use regression testing to maintain our =
standards compliance gains.
23WebKit aims for compliance with relevant web standards, and =
support for new standards. In addition to improving compliance, we =
participate in the web standards community to bring new technologies =
into standards, and to make sure new standards are practical to =
implement in our engine. We use regression testing to maintain our =
standards compliance gains.
2424Stability
25 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.
25The 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.
2626Performance
27 Maintaining and improving speed and memory use is an important =
goal. We never consider performance =E2=80=9Cgood enough=E2=80=9D, 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.
27Maintaining and improving speed, memory use, responsiveness, and =
consistent frame rate is an important goal. We never consider =
performance =E2=80=9Cgood enough=E2=80=9D, 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.
28Battery Life
29In addition to traditional performance metrics, we aim to minimize =
power consumption to maximize browsing battery life for portable =
devices.
2830Security
2931Protecting users from security violations is critical. We fix =
security issues promptly to protect users and maintain their trust.
32Privacy
33We 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.
3034Portability
31 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.
35The 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.
3236Usability
3337To the extent that WebKit features affect the user experience, we =
want them to work in accordance with good human interface design =
principles, and to mesh well with platform-native HI conventions. =
Furthermore, we strive to integrate with platform accessibility features =
to allow access for all users, including those with disabilities.
3438Hackability
----------------------
The WebKit Open Source Project
WebKit is an open source Web content engine for browsers and other =
applications.
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).
<>Project Goals
<>Web Content Engine
The project=E2=80=99s 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.
<>Open Source
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 chat room and a public mailing list where the =
ideas of contributors both new and old are heard and discussed with =
equal weight.
<>Compatibility
For users browsing the web, compatibility with their existing sites is =
essential. We strive to maintain and improve compatibility with existing =
web content, sometimes even at the expense of standards. We use =
regression testing to maintain our compatibility gains.
<>Standards Compliance
WebKit aims for compliance with relevant web standards, and support for =
new standards. In addition to improving compliance, we participate in =
the web standards community to bring new technologies into standards, =
and to make sure new standards are practical to implement in our engine. =
We use regression testing to maintain our standards compliance gains.
<>Stability
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.
<>Performance
Maintaining and improving speed, memory use, responsiveness, and =
consistent frame rate is an important goal. We never consider =
performance =E2=80=9Cgood enough=E2=80=9D, 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.
<>Battery Life
In addition to traditional performance metrics, we aim to minimize power =
consumption to maximize browsing battery life for portable devices.
<>Security
Protecting users from security violations is critical. We fix security =
issues promptly to protect users and maintain their trust.
<>Privacy
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.
<>Portability
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.
<>Usability
To the extent that WebKit features affect the user experience, we want =
them to work in accordance with good human interface design principles, =
and to mesh well with platform-native HI conventions. Furthermore, we =
strive to integrate with platform accessibility features to allow access =
for all users, including those with disabilities.
<>Hackability
To make rapid progress possible, we try to keep the code relatively easy =
to understand, even though web technologies are often complex. We try to =
use straightforward algorithms and data structures when possible, we try =
to write clear, maintainable code, and we continue to improve names and =
code structure to aid understanding. When tricky =E2=80=9Crocket =
science=E2=80=9D code is truly needed to solve some problem, we try to =
keep it bottled up behind clean interfaces. In addition, we make heavy =
use of automated regression tests as a safety net, to allow aggressive =
changes with less risk of regressions.
<>What WebKit is Not
There are a few points that arise occasionally which we consider out of =
scope for the project.
<>WebKit is an engine, not a browser.
We do not plan to develop or host a full-featured web browser based on =
WebKit. Others are welcome to do so, of course.
<>WebKit is an engineering project not a science project.
For new features to be adopted into WebKit, we strongly prefer for the =
technology or at least the use case for it to be proven.
<>WebKit is not a bundle of maximally general and reusable code.
We build some general-purpose parts, but only to the degree needed to be =
a good web content engine.
<>WebKit is not the solution to every problem.
We focus on web content, not complete solutions to every imaginable =
technology need.=
--Apple-Mail=_9462F648-BAE3-4864-B995-AE06A108F753
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=utf-8
New version, with Oxford comma everywhere. I didn=E2=80=99=
t add the use of =E2=80=9Citself=E2=80=9D because I don=E2=80=99t think =
the sentence is ambiguous as written, given the second clause. And if it =
is ambiguous, =E2=80=9Citself=E2=80=9D would not remove the =
ambiguity.
Below the =
diff, there=E2=80=99s the full text of the page as it would appear with =
these diffs applied (though without styling).
project-new.html
1111 WebKit is an open =
source Web content engine for browsers and other =
applications.
1212</p></blockquote>
1313<p><img =
src=3D"/wp-content/themes/webkit/images/webkit.svg" alt=3D"The WebKit =
Project Logo" class=3D"aligncenter size-full wp-image-4290" =
width=3D"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=3D"project-goals"></a>Project =
Goals</h2>
1616<h4><a =
name=3D"web-content-engine"></a>Web Content =
Engine</h4>
17 <p>The project=E2=80=99s 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=E2=80=99s 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=3D"open-source"></a>Open =
Source</h4>
19 <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>
19<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 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=3D"compatibility"></a>Compatibility</h4>
<=
div class=3D"Line LineContainer" style=3D"white-space: nowrap;">
2121<p>For users =
browsing the web, compatibility with their existing sites is essential. =
We strive to maintain and improve compatibility with existing web =
content, sometimes even at the expense of standards. We use regression =
testing to maintain our compatibility gains.</p>2222<h4><a =
name=3D"standards-compliance"></a>Standards =
Compliance</h4>
23 <p>WebKit aims for compliance with relevant web =
standards, and support for new standards In addition to improving =
compliance, we participate in the web standards community to bring new =
technologies into standards, and to make sure new standards are =
practical to implement in our engine. We use regression testing to =
maintain our standards compliance =
gains.</p>
23<p>WebKit aims =
for compliance with relevant web standards, and support for new =
standards. In addition to improving =
compliance, we participate in the web standards community to bring new =
technologies into standards, and to make sure new standards are =
practical to implement in our engine. We use regression testing to =
maintain our standards compliance =
gains.</p>
2424<h4><a =
name=3D"stability"></a>Stability</h4>
25 <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>
25<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=3D"performance"></a>Performance</h4>
27 <p>Maintaining and improving speed and memory use is =
an important goal. We never consider performance =E2=80=9Cgood =
enough=E2=80=9D, 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, memory use, responsiveness, and consistent frame =
rate is an important goal. We never consider performance =E2=80=9Cgood =
enough=E2=80=9D, 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>
28<h4><a =
name=3D"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=3D"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=3D"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=3D"portability"></a>Portability</h4>
31 <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>
35<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=3D"usability"></a>Usability</h4>
3337<p>To the =
extent that WebKit features affect the user experience, we want them to =
work in accordance with good human interface design principles, and to =
mesh well with platform-native HI conventions. Furthermore, we strive to =
integrate with platform accessibility features to allow access for all =
users, including those with disabilities.</p>
3438<h4><a =
name=3D"hackability"></a>Hackability</h4>
----------------------
WebKit is an open source =
Web content engine for browsers and other =
applications.
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).
Project Goals
Web Content Engine
The project=E2=80=99s 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.
Open Source
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 chat room and =
a public mailing list where the ideas of contributors both new and old =
are heard and discussed with equal weight.
Compatibility
For =
users browsing the web, compatibility with their existing sites is =
essential. We strive to maintain and improve compatibility with existing =
web content, sometimes even at the expense of standards. We use =
regression testing to maintain our compatibility gains.
Standards =
Compliance
WebKit aims for compliance with relevant =
web standards, and support for new standards. In addition to improving =
compliance, we participate in the web standards community to bring new =
technologies into standards, and to make sure new standards are =
practical to implement in our engine. We use regression testing to =
maintain our standards compliance gains.
Stability
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.
Performance
Maintaining and improving speed, memory use, responsiveness, =
and consistent frame rate is an important goal. We never consider =
performance =E2=80=9Cgood enough=E2=80=9D, 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.
Battery Life
In =
addition to traditional performance metrics, we aim to minimize power =
consumption to maximize browsing battery life for portable =
devices.
Security
Protecting users from security =
violations is critical. We fix security issues promptly to protect users =
and maintain their trust.
Privacy
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.
Portability
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.
Usability
To the extent that WebKit =
features affect the user experience, we want them to work in accordance =
with good human interface design principles, and to mesh well with =
platform-native HI conventions. Furthermore, we strive to integrate with =
platform accessibility features to allow access for all users, including =
those with disabilities.
Hackability
To make rapid progress =
possible, we try to keep the code relatively easy to understand, even =
though web technologies are often complex. We try to use straightforward =
algorithms and data structures when possible, we try to write clear, =
maintainable code, and we continue to improve names and code structure =
to aid understanding. When tricky =E2=80=9Crocket science=E2=80=9D code =
is truly needed to solve some problem, we try to keep it bottled up =
behind clean interfaces. In addition, we make heavy use of automated =
regression tests as a safety net, to allow aggressive changes with less =
risk of regressions.
What WebKit is Not
There are a few =
points that arise occasionally which we consider out of scope for the =
project.
WebKit is an engine, not a browser.
We =
do not plan to develop or host a full-featured web browser based on =
WebKit. Others are welcome to do so, of course.
WebKit is an engineering project not a science =
project.
For new features to be adopted into WebKit, =
we strongly prefer for the technology or at least the use case for it to =
be proven.
WebKit is not a bundle of maximally general and reusable =
code.
We build some general-purpose parts, but only to =
the degree needed to be a good web content engine.
WebKit=
is not the solution to every problem.
We focus on web =
content, not complete solutions to every imaginable technology =
need.
=
--Apple-Mail=_9462F648-BAE3-4864-B995-AE06A108F753--
--===============0346408819==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev
--===============0346408819==--