Re: [webkit-dev] Proposal: add Privacy to WebKit Project Goals

[Megan Gardner]

 I also like the stronger privacy language.

Megan

> On Feb 24, 2020, at 9:56 AM, Brent Fulgham  wrote:
> 
> I think this looks great!
> -Brent
> 
>> On Feb 23, 2020, at 5:02 PM, Maciej Stachowiak > > wrote:
>> 
>> 
>> V2, with stronger privacy language.
>> 
>> 
>> project-new.html
>>   WebKit is an open source Web content engine for browsers and other 
>> applications.
>> 1212
>> 1313> width="33%">
>> 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’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.
>>  17The 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.
>> 1818Open Source
>> 1919WebKit 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.
>> 2020Compatibility
>> 
>> 2424Stability
>> 2525The 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 “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.
>>  27Maintaining 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.
>>  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
>> 3135The 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
> 
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Proposal: add Privacy to WebKit Project Goals

[Brent Fulgham]

I think this looks great!
-Brent

> On Feb 23, 2020, at 5:02 PM, Maciej Stachowiak  wrote:
> 
> 
> V2, with stronger privacy language.
> 
> 
> project-new.html
>   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’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.
>  17The 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.
> 1818Open Source
> 1919WebKit 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.
> 2020Compatibility
> 
> 2424Stability
> 2525The 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 “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.
>  27Maintaining 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.
>  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
> 3135The 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

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev