Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [GSoC19] Motivation
Date: Mon, 1 Apr 2019 21:44:16 +0200	[thread overview]
Message-ID: <20190401214416.1e265d6f@windsurf> (raw)
In-Reply-To: <CAGCTLNTuWB7E_txmWm9s+fOU5EJsyU1guWNOUM8c40B5WDOoog@mail.gmail.com>

Hello Mohamed,

On Mon, 1 Apr 2019 21:07:15 +0200
Mohamed Dawod <mhm.dawod@gmail.com> wrote:

> I am looking forward to be accepted in this project because I would like to
> dig deeper in this field as I adore it,
> and because it may be my last chance to participate in GSoC, I wouldn't
> like to lose this chance.

Thanks a lot for introducing yourself, and for your interest in our
topic related to IceCC.

In order to show your interest and skills, could you try to submit one
patch doing some useful contribution to Buildroot ?

You could for example look at http://autobuild.buildroot.net/stats/ for
some package that is not up-to-date, update it to a newer version, test
it on some target (real HW or Qemu) and provide a patch doing the
update. Of course, make sure to read a bit the mailing list to see the
best practices. Check out also the Buildroot manual which has some
indications on how to contribute.

Alternatively, you could have a look at http://autobuild.buildroot.net/
and try to solve some of the build failures, but this is more difficult
for a newcomer.

Thanks!

Thomas Petazzoni
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-04-01 19:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-01 19:07 [Buildroot] [GSoC19] Motivation Mohamed Dawod
2019-04-01 19:44 ` Thomas Petazzoni [this message]
2019-04-02  3:14   ` Mohamed Dawod
2019-04-03 22:14     ` Mohamed Dawod
2019-04-04  5:56       ` Peter Korsgaard
2019-04-04  7:08         ` Mohamed Dawod
2019-04-04 10:11           ` 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=20190401214416.1e265d6f@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --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