Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1 of 2 for-2014.05] website: rework Contribute page to avoid duplication with manual
Date: Sat, 24 May 2014 19:53:04 +0200	[thread overview]
Message-ID: <20140524175304.GB3491@free.fr> (raw)
In-Reply-To: <e4de9008424efcd20319.1400951994@argentina>

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

  reply	other threads:[~2014-05-24 17:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-24 17:19 [Buildroot] [PATCH 0 of 2 for-2014.05] website: some limited updates Thomas De Schampheleire
2014-05-24 17:19 ` [Buildroot] [PATCH 1 of 2 for-2014.05] website: rework Contribute page to avoid duplication with manual Thomas De Schampheleire
2014-05-24 17:53   ` Yann E. MORIN [this message]
2014-05-24 17:19 ` [Buildroot] [PATCH 2 of 2 for-2014.05] website: remove remaining references to uclibc.org Thomas De Schampheleire
2014-05-24 17:32   ` Yann E. MORIN

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140524175304.GB3491@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox