[Buildroot] [PATCH 0 of 2 for-2014.05] website: some limited updates

[Buildroot] [PATCH 0 of 2 for-2014.05] website: some limited updates

[Thomas De Schampheleire]

These two patches make two updates to the buildroot website:
- update contribute page
- remove references to uclibc.org

Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>

---
 docs/contribute.html |  53 ++++++++++++++++++++--------------------------
 docs/docs.html       |   2 +-
 docs/js/buildroot.js |   2 +-
 docs/support.html    |   2 +-
 4 files changed, 26 insertions(+), 33 deletions(-)


Note: it seems that lists.buildroot.org forwards to bugs.busybox.net instead
of staying at lists, which makes the list URL unchangeable, currently.

[Buildroot] [PATCH 1 of 2 for-2014.05] website: rework Contribute page to avoid duplication with manual

[Thomas De Schampheleire]

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 <thomas.de.schampheleire@gmail.com>

---
 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.

diff --git a/docs/contribute.html b/docs/contribute.html
--- a/docs/contribute.html
+++ b/docs/contribute.html
@@ -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>.
 
 <!--#include file="footer.html" -->

[Buildroot] [PATCH 1 of 2 for-2014.05] website: rework Contribute page to avoid duplication with manual

[Yann E. MORIN]

Thomas, All,

On 2014-05-24 19:19 +0200, Thomas De Schampheleire spake thusly:
> 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 <thomas.de.schampheleire@gmail.com>

Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>

Regards,
Yann E. MORIN.

> ---
>  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.
> 
> diff --git a/docs/contribute.html b/docs/contribute.html
> --- a/docs/contribute.html
> +++ b/docs/contribute.html
> @@ -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>.
>  
>  <!--#include file="footer.html" -->
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

[Buildroot] [PATCH 2 of 2 for-2014.05] website: remove remaining references to uclibc.org

[Thomas De Schampheleire]

The website still used some uclibc.org URLs which can now use buildroot.org.

Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>

---
 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...

diff --git a/docs/docs.html b/docs/docs.html
--- a/docs/docs.html
+++ b/docs/docs.html
@@ -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>
diff --git a/docs/js/buildroot.js b/docs/js/buildroot.js
--- a/docs/js/buildroot.js
+++ b/docs/js/buildroot.js
@@ -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() {
diff --git a/docs/support.html b/docs/support.html
--- a/docs/support.html
+++ b/docs/support.html
@@ -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.

[Buildroot] [PATCH 2 of 2 for-2014.05] website: remove remaining references to uclibc.org

[Yann E. MORIN]

Thomas, All,

On 2014-05-24 19:19 +0200, Thomas De Schampheleire spake thusly:
> The website still used some uclibc.org URLs which can now use buildroot.org.
> 
> Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>

With the minor not below fixed:
    Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>

> ---
>  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...
> 
> diff --git a/docs/docs.html b/docs/docs.html
> --- a/docs/docs.html
> +++ b/docs/docs.html
> @@ -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>
> diff --git a/docs/js/buildroot.js b/docs/js/buildroot.js
> --- a/docs/js/buildroot.js
> +++ b/docs/js/buildroot.js
> @@ -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() {
> diff --git a/docs/support.html b/docs/support.html
> --- a/docs/support.html
> +++ b/docs/support.html
> @@ -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>
                               ^
While you are at it, this should be a singular.

Regards,
Yann E. MORIN.

>  to post your bugs and/or participate to find solutions to existing problems.
>  
>  Note: Patch are only accepted through the mailing list.
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'