Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Google Summer of Code 2018 ?
Date: Wed, 17 Jan 2018 21:52:08 +0100	[thread overview]
Message-ID: <20180117215208.45dd61b9@windsurf> (raw)

Hello,

For information, organizations can apply for GSoC 2018 until January
23, so there is less than a week left to apply. The questions are: do
we want to apply? And if yes, for what topics?

Looking at https://elinux.org/Buildroot:GSoC2017Ideas:

 - Reproducible builds. While some initial work was done, there is
   definitely a lot more that could be done.

 - Testing infrastructure: the runtime testing infrastructure was
   added in the mean time. Writing more tests and extending the
   infrastructure is still needed though.

 - Relocatable SDK: this topic is pretty much solved IMO, so this topic
   is no longer relevant.

 - Follow upstream updates and CVEs of packages. I think this topic is
   still relevant, and IMO is the most interesting topic.

 - Support for LLVM: an intern from Smile (France) just announced that
   he will be working on this topic during the next months, so I don't
   see the point of having a GSOC on the same topic.

 - Support new languages and complete existing ones. I'm not sure about
   this one:
   * For NodeJS, I'm not sure we want to have zillions of packages for
     the different NodeJS modules
   * The Go package infrastructure has been resubmitted, and is
     actively being pushed by Angelo
   * The Rust support is actively being pushed by Eric
   So I don't know if there's enough things left to do for this project
   idea.

Any other idea of what's missing in Buildroot, or that could be
improved ?

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

             reply	other threads:[~2018-01-17 20:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-17 20:52 Thomas Petazzoni [this message]
2018-01-17 22:50 ` [Buildroot] Google Summer of Code 2018 ? Matthew Weber
2018-01-18  7:51   ` Thomas Petazzoni
2018-01-18 15:52     ` Matthew Weber
2018-01-18 22:43       ` Matthew Weber
2018-01-22 22:04 ` Arnout Vandecappelle
2018-01-23 18:00   ` Matthew Weber
2018-01-24  8:00     ` 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=20180117215208.45dd61b9@windsurf \
    --to=thomas.petazzoni@free-electrons.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