website: some limited updates
PATCH v2 1/1 website: some limited updates
These patches make a few updates to the buildroot website:
- update contribute and support page
- remove references to uclibc.org
- add alt property to img tags (correct html)
--- docs/contribute.html | 53 ++++++++++++++++++++-------------------------- docs/docs.html | 2 +- docs/header.html | 3 ++- docs/index.html | 3 ++- docs/js/buildroot.js | 2 +- docs/support.html | 32 ++++++++++++++++----------------
Note: it seems that lists.buildroot.org forwards to bugs.busybox.net instead of staying at lists, which makes the list URL unchangeable, currently.
PATCH v2 1/1 website: rework Contribute page to avoid duplication with manual
The manual contains details about how users can contribute to buildroot. The website also had such a list, but with much less detail and not containing all topics.
In order to avoid duplicating this information, simply list the different topics without detail on the website, and add a link to the relevent chapter of the manual.
---
v2: add missing closing </p> tag in last paragraph
docs/contribute.html | 53 ++++++++++++++++++++-------------------------- 1 files changed, 23 insertions(+), 30 deletions(-)
Note: the current manual does not have the updated info. At this instant the info is still on the git version of the manual:
http://nightly.buildroot.org/manual.html#_contributing_to_buildroot
When the 2014.05 release is made, the manual will be updated and all will be well.
docs/contribute.html +23 -30
@@ -2,38 +2,31 @@ <h2>Contribute</h2> -Buildroot is an open source project and if you want to contribute, here a few -pointers to get you started. +<p>Buildroot is an open source project and you are very welcome to contribute to +it.<br /> +There are many different ways to contribute:</p> -<p>Don't forget to look at <a href="./support.html">Support</a> if you need any -help. -And thanks for your help !</p> +<ul> +<li>Reproducing, analyzing and fixing bugs from our + <a href="https://bugs.buildroot.org/">bug tracker</a></li> +<li>Analyzing and fixing <a href="http://autobuild.buildroot.org/"> + autobuild failures</a></li> +<li>Reviewing and testing patches sent by other developers. See the + <a href="http://lists.busybox.net/mailman/listinfo/buildroot">mailing list + </a> or <a href="http://patchwork.ozlabs.org/project/buildroot/list/"> + patchwork</a>.</li> +<li>Working on items from the + <a href="http://www.elinux.org/Buildroot#Todo_list">TODO list</a></li> +<li>Submitting your own patches through the + <a href="http://lists.busybox.net/mailman/listinfo/buildroot">mailing list + </a></li> +</ul> -<h3>Autobuilders</h3> +<p>For more details on these topics, check out chapter +<a href="http://buildroot.uclibc.org/downloads/manual/manual.html#_contributing_to_buildroot"> +Contributing to buildroot</a> in the Buildroot manual. Thanks for your help!</p> -The <a href="http://autobuild.buildroot.org/">Autobuilders</a> are used to test -Buildroot with a lot of differents settings (toolchains, various packages, etc) -on all the supported platforms. - -<p>But despite our best effort, sometimes it fails.</p> -<p>That's where you can help ! Look at a package that fails and try to fix it !</p> - -<h3>Wiki</h3> - -Have a look at the <a href="http://elinux.org/Buildroot">eLinux Wiki</a> a todo -list is available there, which can help you find out what you could do to help -Buildroot. - -<h3>Patchwork</h3> - -<a href="http://patchwork.ozlabs.org/project/buildroot/list/">Patchwork</a> -is a patch tracking system, if you submit a patch, it will appear here. - -<p>You can have a look at a patch that interests you and test it on your machine, -if it succeeds, you can send a <a - href="http://buildroot.org/downloads/manual/manual.html#_reviewing_testing_patches">"Tested-by"</a>, -if it fails, you can also send a mail on the <a - href="http://buildroot.org/downloads/manual/manual.html#_mailing_list">mailing - list</a> and report what has happened to you.</p> +<p>If you need any support yourself, have a look at <a href="./support.html"> +Support</a>.</p> <!--#include file="footer.html" -->
PATCH v2 1/1 website: rework Contribute page to avoid duplication with manual
Quoted 49 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Thomas" == Thomas De Schampheleire <[email protected]> writes:
The manual contains details about how users can contribute to buildroot. The website also had such a list, but with much less detail and not containing all topics.
In order to avoid duplicating this information, simply list the different topics without detail on the website, and add a link to the relevent chapter of the manual.Signed-off-by Thomas De Schampheleire <[email protected]>---
v2: add missing closing </p> tag in last paragraphdocs/contribute.html | 53 ++++++++++++++++++++-------------------------- 1 files changed, 23 insertions(+), 30 deletions(-)Note: the current manual does not have the updated info. At this instant the info is still on the git version of the manual:
http://nightly.buildroot.org/manual.html#_contributing_to_buildroot
When the 2014.05 release is made, the manual will be updated and all will be well.docs/contribute.html +13
-5@@ -2,38 +2,31 @@ <h2>Contribute</h2> -Buildroot is an open source project and if you want to contribute, here a few -pointers to get you started. +<p>Buildroot is an open source project and you are very welcome to contribute to +it.<br /> +There are many different ways to contribute:</p> -<p>Don't forget to look at <a href="./support.html">Support</a> if you need any -help. -And thanks for your help !</p> +<ul> +<li>Reproducing, analyzing and fixing bugs from our + <a href="https://bugs.buildroot.org/">bug tracker</a></li> +<li>Analyzing and fixing <a href="http://autobuild.buildroot.org/"> + autobuild failures</a></li> +<li>Reviewing and testing patches sent by other developers. See the + <a href="http://lists.busybox.net/mailman/listinfo/buildroot">mailing list + </a> or <a href="http://patchwork.ozlabs.org/project/buildroot/list/"> + patchwork</a>.</li> +<li>Working on items from the
docs/contribute.html line 27
Quoted 10 lines
docs/contribute.html +8
-1+ <a href="http://www.elinux.org/Buildroot#Todo_list">TODO list</a></li> +<li>Submitting your own patches through the + <a href="http://lists.busybox.net/mailman/listinfo/buildroot">mailing list + </a></li> +</ul> -<h3>Autobuilders</h3> +<p>For more details on these topics, check out chapter +<a href="http://buildroot.uclibc.org/downloads/manual/manual.html#_contributing_to_buildroot"> +Contributing to buildroot</a> in the Buildroot manual. Thanks for your help!</p>
I've changed this to 'check out the <a href=..>Contributing to buildroot</a> chapter in the Buildroot manual' and committed, thanks.
Signature · 1 line
Bye, Peter Korsgaard
PATCH v2 1/1 website: remove remaining references to uclibc.org
In reply to Thomas De SchampheleireThe website still used some uclibc.org URLs which can now use buildroot.org.
---
v2: no changes
docs/docs.html | 2 +- docs/js/buildroot.js | 2 +- docs/support.html | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)
Note: the news.html page still uses bugs.uclibc.org instead of bugs.buildroot.org, which I was hesitant to change ("you can't rewrite the past"). However, I would like to request Peter if upcoming release announcements could start using bugs.buildroot.org instead...
Note2: Yann's comment on this patch has been integrated in the next patch, along with some other changes
docs/docs.html +1 -1
@@ -34,7 +34,7 @@ help:</p> <li>On the <a href="irc://freenode.net/#buildroot">Buildroot IRC channel</a>, <code>#buildroot</code> on Freenode</li> - <li>On our <a href="https://bugs.uclibc.org">bugtracker</a>.</li> + <li>On our <a href="https://bugs.buildroot.org">bugtracker</a>.</li> <li>Through the various companies offering commercial Buildroot support.</li>
docs/js/buildroot.js +1 -1
@@ -36,7 +36,7 @@ function load_activity(feedurl, divid) { function initialize() { load_activity("http://rss.gmane.org/topics/excerpts/gmane.comp.lib.uclibc.buildroot", "mailing-list-activity"); - load_activity("http://git.uclibc.org/buildroot/atom/?h=master", "commit-activity"); + load_activity("http://git.buildroot.org/buildroot/atom/?h=master", "commit-activity"); } function google_analytics() {
docs/support.html +1 -1
@@ -37,7 +37,7 @@ list with frequently asked questions... <h3>Bug Tracker</h3> -If you encounter any problems while using Buildroot, you can use the <a href="https://bugs.uclibc.org/">Bug Tracker</a> +If you encounter any problems while using Buildroot, you can use the <a href="https://bugs.buildroot.org/">Bug Tracker</a> to post your bugs and/or participate to find solutions to existing problems. Note: Patch are only accepted through the mailing list.
PATCH v2 1/1 website: remove remaining references to uclibc.org
Quoted 5 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Thomas" == Thomas De Schampheleire <[email protected]> writes:
The website still used some uclibc.org URLs which can now use buildroot.org.
Signed-off-by Thomas De Schampheleire <[email protected]>Reviewed-by "Yann E. MORIN" <[email protected]>
Committed, thanks.
Signature · 1 line
Bye, Peter Korsgaard
PATCH v2 1/1 website: fix typos and HTML on support page
In reply to Thomas De SchampheleireFix a few typos on the support page, and add correct HTML <p> </p> tag pairs.
---
v2: new patch
docs/support.html | 32 ++++++++++++++++---------------- 1 files changed, 16 insertions(+), 16 deletions(-)
docs/support.html +16 -16
@@ -2,32 +2,31 @@ <h2>Support</h2> -You can get support for Buildroot through three main channels: +<p>You can get support for Buildroot through three main channels:</p> <h3>IRC</h3> -The Buildroot IRC is <a href="irc://freenode.net/#buildroot">#buildroot</a>. -The channel #buildroot is hosted on Freenode <a href="http://webchat.freenode.net">WebChat</a>. - +<p>The Buildroot IRC channel is <a href="irc://freenode.net/#buildroot"> +#buildroot</a>, hosted on Freenode. If you do not have an IRC client, you can +use the <a href="http://webchat.freenode.net">Freenode web interface</a>. When asking for help on IRC, share relevant logs or pieces of code using a code -sharing website. +sharing website.</p> <h3>Mailing List Information</h3> -The <a href="/lists/buildroot/">mailing list</a> is for discussion and +<p>The <a href="/lists/buildroot/">mailing list</a> is for discussion and development. You can subscribe by visiting <a href="http://lists.busybox.net/mailman/listinfo/buildroot">this page</a>. Only subscribers to the Buildroot mailing list are allowed to post -to this list. -<p> -The list is also available through <a +to this list.</p> + +<p>The list is also available through <a href="http://gmane.org">Gmane</a> at <a href="http://dir.gmane.org/gmane.comp.lib.uclibc.buildroot">gmane.comp.lib.uclibc.buildroot</a>. -<p> +</p> <h4>Search the List Archives</h4> -Please search the mailing list archives before asking questions on the mailing +<p>Please search the mailing list archives before asking questions on the mailing list, since there is a good chance someone else has asked the same question before. Checking the archives is a great way to avoid annoying everyone on the -list with frequently asked questions... -<p> +list with frequently asked questions...</p> <form method="get" action="http://search.gmane.org/"> <input type="text" name="query">
@@ -37,9 +36,10 @@ list with frequently asked questions... <h3>Bug Tracker</h3> -If you encounter any problems while using Buildroot, you can use the <a href="https://bugs.buildroot.org/">Bug Tracker</a> -to post your bugs and/or participate to find solutions to existing problems. +<p>If you encounter any problem while using Buildroot, you can use the +<a href="https://bugs.buildroot.org/">Bug Tracker</a> to post your bugs and/or +participate to find solutions to existing problems.</p> -Note: Patch are only accepted through the mailing list. +<p>Note: patches are only accepted through the mailing list.</p> <!--#include file="footer.html" -->
PATCH v2 1/1 website: fix typos and HTML on support page
Quoted 9 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Thomas" == Thomas De Schampheleire <[email protected]> writes:
Fix a few typos on the support page, and add correct HTML <p> </p> tag pairs.
Signed-off-by Thomas De Schampheleire <[email protected]>---
v2: new patch
Committed, thanks.
Signature · 1 line
Bye, Peter Korsgaard
PATCH v2 1/1 website: add alt-tags to images
In reply to Thomas De Schampheleire---
v2: new patch
docs/header.html | 3 ++- docs/index.html | 3 ++- 2 files changed, 4 insertions(+), 2 deletions(-)
docs/header.html +2 -1
@@ -47,7 +47,8 @@ <li><a href="/contribute.html">Contribute</a></li> <li><a href="/sponsors.html">Sponsors</a></li> </ul> - <a class="gplus" href="https://plus.google.com/100084591154899263420/posts"><img src="images/gplus.png" height="28" width="28"></a> + <a class="gplus" href="https://plus.google.com/100084591154899263420/posts"> + <img src="images/gplus.png" height="28" width="28" alt="Google+" /></a> </div><!--/.nav-collapse --> </div> </div>
docs/index.html +2 -1
@@ -2,7 +2,8 @@ <div class="hero-unit"> <div class="row-fluid"> - <img src="images/logo.png" height="170" width="170" style="float: right;"/> + <img src="images/logo.png" height="170" width="170" style="float: right;" + alt="Buildroot logo" /> <div class="span8"> <h1>Buildroot<br/><small>Making Embedded Linux Easy</small></h1> <p>Buildroot is a simple, efficient and easy-to-use tool to generate
PATCH v2 1/1 website: add alt-tags to images
Quoted 5 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Thomas" == Thomas De Schampheleire <[email protected]> writes:
Signed-off-by Thomas De Schampheleire <[email protected]>---
v2: new patch
Committed, thanks.
Signature · 1 line
Bye, Peter Korsgaard