summaryrefslogtreecommitdiff
path: root/developers/gsoc/2014ideas.html
diff options
context:
space:
mode:
Diffstat (limited to 'developers/gsoc/2014ideas.html')
-rw-r--r--developers/gsoc/2014ideas.html16
1 files changed, 8 insertions, 8 deletions
diff --git a/developers/gsoc/2014ideas.html b/developers/gsoc/2014ideas.html
index e159604..d57ba4b 100644
--- a/developers/gsoc/2014ideas.html
+++ b/developers/gsoc/2014ideas.html
@@ -37,8 +37,8 @@
<div class="navsection">
<ul class="sitelinks">
-<li><a href="http://wiki.netsurf-browser.org/">Development wiki</a></li>
-<li><a href="http://source.netsurf-browser.org/">Git repository viewer</a></li>
+<li><a href="//wiki.netsurf-browser.org/">Development wiki</a></li>
+<li><a href="//source.netsurf-browser.org/">Git repository viewer</a></li>
<li><a href="http://ci.netsurf-browser.org/">Continuous Integration</a></li>
<li><a href="http://bugs.netsurf-browser.org/">Bug report system</a></li>
<li><a href="http://ci.netsurf-browser.org/jenkins/view/Categorized/job/docs-netsurf/doxygen/">Code documentation</a></li>
@@ -59,10 +59,10 @@
<dt>Before applying for a project<dt>
<dd>
<ul>
-<li>Get up to speed with <a href="http://wiki.netsurf-browser.org/Documentation/GettingCoding">Git</a>, as we use this for source control, and get the NetSurf <a href="http://www.netsurf-browser.org/documentation/develop#SourceControl">source code</a>. Here are a couple of articles that may help you get started with the NetSurf codebase: <a href="http://vincentsanders.blogspot.co.uk/2013/03/the-way-to-get-started-is-to-quit.html">Getting &amp; building the source</a>, and <a href="http://vincentsanders.blogspot.co.uk/2013/03/man-cannot-discover-new-oceans-unless.html">Working with the codebase and community</a>.</li>
+<li>Get up to speed with <a href="//wiki.netsurf-browser.org/Documentation/GettingCoding">Git</a>, as we use this for source control, and get the NetSurf <a href="http://www.netsurf-browser.org/documentation/develop#SourceControl">source code</a>. Here are a couple of articles that may help you get started with the NetSurf codebase: <a href="http://vincentsanders.blogspot.co.uk/2013/03/the-way-to-get-started-is-to-quit.html">Getting &amp; building the source</a>, and <a href="http://vincentsanders.blogspot.co.uk/2013/03/man-cannot-discover-new-oceans-unless.html">Working with the codebase and community</a>.</li>
<li><a href="http://www.netsurf-browser.org/documentation/develop#Compiling">Build NetSurf</a> and enjoy using it. (Ask on IRC if you need help.)</li>
<li>Join our IRC channel <code>#netsurf</code> on <a href="http://freenode.net/">Freenode</a> and introduce yourself. Also, subscribe to the <a href="http://www.netsurf-browser.org/lists/netsurf-dev">developer mailing list</a>.</li>
-<li>Get familiarised with the source code &ndash; read the <a href="http://source.netsurf-browser.org/netsurf.git/tree/docs">code documentation</a>.</li>
+<li>Get familiarised with the source code &ndash; read the <a href="//source.netsurf-browser.org/netsurf.git/tree/docs">code documentation</a>.</li>
<li>Consider submitting a patch to fix an issue on our <a href="http://bugs.netsurf-browser.org/">bug tracker</a>.</li>
<li>Ideally students will have a dialogue with us about what they intend to do, before they make their application.</li>
</ul>
@@ -87,7 +87,7 @@
</dd>
</dl>
-<p>There is some more information in the <a href="http://wiki.netsurf-browser.org/google-summer-of-code">GSoC section</a> of our wiki. Note particularly the <a href="http://wiki.netsurf-browser.org/gsoc-student-guidelines">student guidelines</a>.</p>
+<p>There is some more information in the <a href="//wiki.netsurf-browser.org/google-summer-of-code">GSoC section</a> of our wiki. Note particularly the <a href="http://wiki.netsurf-browser.org/gsoc-student-guidelines">student guidelines</a>.</p>
<p>Please <a href="/contact/">get in touch</a> our project idea appeals to you or if you have your own idea for either <a href="/">NetSurf</a> or one of NetSurf's <a href="/projects/">libraries</a>. Come and chat to the developers in the NetSurf IRC channel or post to the developer mailing list.</p>
@@ -110,7 +110,7 @@
<p>We consider this task to be fairly easy to complete. The number of missing specialisations is quite large, so do not be surprised if it takes longer than expected! We do not expect this phase to fill an entire summer, however.</p>
<p>Expected outcome: a complete implementation of the HTMLElement DOM classes, which enable the HTMLElement tests in the LibDOM testsuite to pass.</p>
</dd>
-<p><strong>Existing code:</strong> <a href="http://git.netsurf-browser.org/libdom.git/tree/src/html">libdom/src/html</a>.<br><strong>Specification:</strong> <a href="http://www.w3.org/TR/2003/REC-DOM-Level-2-HTML-20030109/idl-definitions.html">Level 2 Document Object Model HTML</a>, <a href="http://dom.spec.whatwg.org/">DOM Standard</a></p>
+<p><strong>Existing code:</strong> <a href="//git.netsurf-browser.org/libdom.git/tree/src/html">libdom/src/html</a>.<br><strong>Specification:</strong> <a href="http://www.w3.org/TR/2003/REC-DOM-Level-2-HTML-20030109/idl-definitions.html">Level 2 Document Object Model HTML</a>, <a href="http://dom.spec.whatwg.org/">DOM Standard</a></p>
</dd>
</dl>
<h4>Phase 2</h4>
@@ -123,7 +123,7 @@
<p>This task involves identifying the differences between the behaviour implemented in LibHubbub and the expected behaviour defined by the specification. Once these differences have been identified, the implementation in LibHubbub should be brought in line with the specification.</p>
<p>We expect this task to require a great deal of attention to detail. The initial stage of identifying the places where LibHubbub's implementation does not match the specification is crucial to the success of this task.</p>
<p>Expected outcome: a detailed summary of the deficiencies in the LibHubbub implementation and a decent amount of progress towards rectifying them, with passing tests in the testsuite.</p>
-<p><strong>Existing code:</strong> <a href="http://git.netsurf-browser.org/libhubbub.git/tree/">libhubbub/src</a><br><strong>Specification:</strong> <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/parsing.html">HTML5 Parsing</a></p>
+<p><strong>Existing code:</strong> <a href="//git.netsurf-browser.org/libhubbub.git/tree/">libhubbub/src</a><br><strong>Specification:</strong> <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/parsing.html">HTML5 Parsing</a></p>
</dd>
<dt>LibCSS: add support for CSS 3 properties</dt>
<dd>
@@ -138,7 +138,7 @@
</ul>
<p>This task involves adding support for parsing and selecting properties defined in other CSS 3 module specifications. As CSS 3 is comprised of a very broad suite of components, the precise selection of which modules to target will be decided as part of the task definition with the student.</p>
<p>Expected outcome: a decision about which CSS 3 component modules to implement; an implementation of the relevant property parsing and selection rules, along with passing test cases for the LibCSS testsuite.</p>
-<p><strong>Existing code:</strong> <a href="http://git.netsurf-browser.org/libcss.git/tree/src">libcss/src</a><br><strong>Specification:</strong> <a href="http://www.w3.org/Style/CSS/specs.en.html">CSS Specs</a></p>
+<p><strong>Existing code:</strong> <a href="//git.netsurf-browser.org/libcss.git/tree/src">libcss/src</a><br><strong>Specification:</strong> <a href="http://www.w3.org/Style/CSS/specs.en.html">CSS Specs</a></p>
</li>
</dl>
<p><strong>Skills required:</strong> Experience of the C programming language<br><strong>Skills desirable:</strong> HTML, DOM, CSS