1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
|
<!--
SPDX-FileCopyrightText: The WebKit GTK and WPE teams
SPDX-License-Identifier: BSD, LGPL-2.1
-->
<!DOCTYPE html>
<html lang="en">
<head>
<title>WPEWebKit – 2.0: Pointers for contribution</title>
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta charset="utf-8" />
<meta property="og:type" content="website"/>
<meta property="og:title" content="WPEWebKit: Pointers for contribution"/>
<meta property="og:description" content="Reference for WPEWebKit-2.0: Pointers for contribution"/>
<meta name="twitter:title" content="WPEWebKit: Pointers for contribution"/>
<meta name="twitter:description" content="Reference for WPEWebKit-2.0: Pointers for contribution"/>
<meta name="twitter:card" content="summary"/>
<link rel="stylesheet" href="style.css" type="text/css" />
<script src="wpe2-urlmap.js"></script>
<script src="fzy.js"></script>
<script src="search.js"></script>
<script src="main.js"></script>
</head>
<body>
<div id="body-wrapper" tabindex="-1">
<nav class="sidebar devhelp-hidden">
<div class="search section">
<form id="search-form" autocomplete="off">
<input id="search-input" type="text" name="do-not-autocomplete" placeholder="Click, or press 's' to search" autocomplete="off"/>
</form>
</div>
<div class="section namespace">
<h3><a href="index.html">WPEWebKit</a></h3>
<p>API Version: 2.0</p>
<p>Library Version: 2.50.5</p>
</div>
<div class="section generator">
<p>Generated by <a href="https://gitlab.gnome.org/GNOME/gi-docgen">gi-docgen</a> 2023.1</p>
</div>
</nav>
<button id="btn-to-top" class="hidden"><span class="up-arrow"></span></button>
<section id="main" class="content">
<section>
<div class="docblock">
<h2 id="contacting-us">Contacting Us<a class="md-anchor" href="#contacting-us" title="Permanent link"></a></h2>
<p>You can find the developers behind <span class="caps">WPE</span> WebKit on various platforms:</p>
<ul>
<li><a href="https://floss.social/WPEWebKit">Mastodon</a>.</li>
<li><a href="https://bsky.app/profile/wpewebkit.org">Bluesky</a>.</li>
<li><a href="https://matrix.to/#/#wpe:matrix.org">#wpe channel</a> on <strong>Matrix</strong>.</li>
<li><a href="https://webchat.oftc.net/?channels=wpe">#wpe channel</a> on the <strong><span class="caps">OTFC</span></strong> <span class="caps">IRC</span> network (bridged to the Matrix one).</li>
</ul>
<p>Feel free to reach out to us if you have any questions. For reporting issues and requesting new features, please follow the contribution guidelines in the following section.</p>
<h2 id="reporting-feedback">Reporting Feedback<a class="md-anchor" href="#reporting-feedback" title="Permanent link"></a></h2>
<p>If you encountered a bug, an unusual behavior, or would like to request a new feature, the <a href="https://bugs.webkit.org">WebKit Bugzilla</a> is the place to visit. Bugs specific to the <span class="caps">GTK</span> and <span class="caps">WPE</span> ports, as well as cross-platform bugs affecting all WebKit ports (including e.g. macOS/iOS variants), are reported there.</p>
<p>WebKit is a large software project with many contributors and billions of users, receiving a lot of bug reports. Before reporting a new issue, be sure to <a href="https://bugs.webkit.org/query.cgi">search for the existing ones</a> to make sure your issue may be already known. However, do not refrain from opening a ticket if you cannot find any describing your issue.</p>
<p>If you are unfamiliar with the <a href="https://bugs.webkit.org/page.cgi?id=bug-writing.html">WebKit bug writing guidelines</a>, you might want to have a look before opening a ticket. Prefix the bug title with <strong>[<span class="caps">WPE</span>]</strong> or <strong>[<span class="caps">GTK</span>]</strong> depending on the port flavour that you are using, and ideally assign a component that matches the problem domain. If unsure, select WebKitGTK or <span class="caps">WPE</span> WebKit, but do not leave it unassigned.</p>
<p>Last but not least, thanks for your contribution! You can make a difference and help us improve and evolve our project.</p>
<h2 id="code-contributions">Code Contributions<a class="md-anchor" href="#code-contributions" title="Permanent link"></a></h2>
<p>To contribute, you should first setup a local development environment. The easiest solution is to use the <a href="https://github.com/Igalia/webkit-container-sdk">WebKit Container <span class="caps">SDK</span></a>. It contains a set of scripts that assist in creating and running a <a href="https://podman.io/">Podman</a>-based container on your Linux machine, which contains all dependencies needed to compile WebKit.</p>
<p>The <strong>webkit.org</strong> page contains a <a href="https://webkit.org/contributing-code/">section</a> dedicated to code contributions—be sure to read it, as it contains many interesting articles, covering the <a href="http://ews-build.webkit.org">WebKit Early Warning System (<span class="caps">EWS</span>)</a>, the <a href="https://webkit.org/code-style-guidelines/">coding style guidelines</a> and much more.</p>
<p>Additionally there is a <a href="https://github.com/WebKit/WebKit/wiki">Wiki</a> page with further information about the WebKit project, and links to all aforementioned pages.</p>
</div>
</section>
</section>
<div id="toc" class="toc">
<nav aria-labelledby="toc-title">
<p id="toc-title">Content</p>
<ul class="toc-list">
<li class="toc-list-item"><a href="#contacting-us"><span class="link-text">Contacting Us</span></a></li>
<li class="toc-list-item"><a href="#reporting-feedback"><span class="link-text">Reporting Feedback</span></a></li>
<li class="toc-list-item"><a href="#code-contributions"><span class="link-text">Code Contributions</span></a></li>
</ul>
</nav>
</div>
<section id="search" class="content hidden"></section>
<footer>
</footer>
</div>
</body>
</html>
|
