[dpdk-web] [PATCH v2 3/3] force HTTPS for logins
Thomas Monjalon
thomas at monjalon.net
Wed Dec 13 16:44:52 CET 2017
Patchwork and bugzilla should be used with HTTPS
to avoid clear-text password login.
Signed-off-by: Thomas Monjalon <thomas at monjalon.net>
---
dev.html | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/dev.html b/dev.html
index 8f6db8d..a539eae 100644
--- a/dev.html
+++ b/dev.html
@@ -42,11 +42,11 @@
<p>Anyone is welcome to contribute.
<p>The collaboration is based on <a href="/browse/">git</a>
and <a href="/ml/archives/dev">emails</a>.
- Coming patches are listed in <a href="/dev/patchwork">patchwork</a>.
+ Coming patches are listed in <a href="https://dpdk.org/dev/patchwork">patchwork</a>.
<p>Planned features are listed in the <a href="/dev/roadmap">roadmap</a>
and integrated during a <a href="/dev/roadmap#cycle">cycle started by a merge window</a>.
<p>Bugs are open in <a
- href="/tracker/buglist.cgi?bug_status=__open__&product=DPDK">bugzilla</a>.
+ href="https://dpdk.org/tracker/buglist.cgi?bug_status=__open__&product=DPDK">bugzilla</a>.
<h3 id="licenses">Licenses</h3>
<p>Main code is BSD licensed and Linux kernel related parts are naturally licensed under the GPL.
@@ -126,7 +126,7 @@
in <a href="/dev/patchwork">patchwork</a> with status <em>"New"</em>.
So they are visible in the default view (filter <em>"Action Required"</em>).
<p>Access to management of his own patches is granted
- after <a href="/dev/patchwork/register">registration</a>.
+ after <a href="https://dpdk.org/dev/patchwork/register">registration</a>.
The status may be manually updated to <em>"RFC"</em>,
<em>"Changes Requested"</em>, <em>"Superseded"</em> or <em>"Rejected"</em>.
After sending a new version of a patch, developers should set
@@ -137,7 +137,7 @@
with a <a href="/dev/patchwork/help/pwclient/">pwclient</a> command line.
<h3 id="bugzilla">Contribute by finding or fixing bugs</h3>
- <p>There is a <a href="/tracker/">bug tracker</a> where
+ <p>There is a <a href="https://dpdk.org/tracker/">bug tracker</a> where
anybody can notify a bug to the community, and follow the resolution.
<p>A notification is sent to dev at dpdk.org for every new bug.
The fixes must be sent and discussed on the mailing list.
--
2.15.0
More information about the web
mailing list