From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1 of 4 v2 for-2014.05] website: rework Contribute page to avoid duplication with manual
Date: Sun, 25 May 2014 21:44:53 +0200 [thread overview]
Message-ID: <8761ktabii.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <b4640a0a0f1e43ba8098.1400962008@argentina> (Thomas De Schampheleire's message of "Sat, 24 May 2014 22:06:48 +0200")
>>>>> "Thomas" == Thomas De Schampheleire <patrickdepinguin@gmail.com> 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 <thomas.de.schampheleire@gmail.com>
> ---
> 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.
> 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>
I've changed this to 'check out the <a href=..>Contributing to
buildroot</a> chapter in the Buildroot manual' and committed, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2014-05-25 19:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-24 20:06 [Buildroot] [PATCH 0 of 4 v2 for-2014.05] website: some limited updates Thomas De Schampheleire
2014-05-24 20:06 ` [Buildroot] [PATCH 1 of 4 v2 for-2014.05] website: rework Contribute page to avoid duplication with manual Thomas De Schampheleire
2014-05-25 19:44 ` Peter Korsgaard [this message]
2014-05-24 20:06 ` [Buildroot] [PATCH 2 of 4 v2 for-2014.05] website: remove remaining references to uclibc.org Thomas De Schampheleire
2014-05-25 19:47 ` Peter Korsgaard
2014-05-24 20:06 ` [Buildroot] [PATCH 3 of 4 v2 for-2014.05] website: fix typos and HTML on support page Thomas De Schampheleire
2014-05-25 19:51 ` Peter Korsgaard
2014-05-24 20:06 ` [Buildroot] [PATCH 4 of 4 v2 for-2014.05] website: add alt-tags to images Thomas De Schampheleire
2014-05-25 19:52 ` Peter Korsgaard
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=8761ktabii.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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