mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: GSoC projects?
Date: Tue, 10 Feb 2015 17:31:10 -0500	[thread overview]
Message-ID: <20150210223110.GA25576@brightrain.aerifal.cx> (raw)

The call for applications for mentoring organizations for Google
Summer of Code 2015 has just opened. While we don't have the
organizational structure for musl to participate directly in GSoC, I'd
like to consider reaching out to some other organizations that might
be able to act as umbrella organizations and offer some possible
projects for students related to musl. Some ideas that come to mind
are:

- Improving toolchain support for musl.

- Fixing portability issues blocking musl support in apps -- the task
  could be something like "make portability fixes for N apps to get
  them working on musl-based systems and get X% of the fixes
  upstream".

- Meaningful benchmarking of libc interfaces that are likely to have
  an impact on performance. (This could be joint with glibc or Bionic,
  even.)

- Packaging more apps for a musl-based dist like Alpine or Sabotage.

- Porting musl to one or more additional archs, possibly covering the
  gaps in target support with musl vs uclibc.

It's been a while since I've looked at GSoC specifics so some of these
might need tweaks to make them into GSoC-worthy projects, but they all
seem like things that would be interesting and valuable.

Do we have anyone from the community who would be interested in
mentoring (or being a student) for projects like this? Other ideas?
Ideas on orgs to reach out to?

Rich


             reply	other threads:[~2015-02-10 22:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-10 22:31 Rich Felker [this message]
2015-02-11  2:03 ` Christopher Meng
2015-02-12  1:59 ` Christopher Meng

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=20150210223110.GA25576@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).