mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Request for volunteers
Date: Sun, 30 Jun 2013 01:52:02 -0400	[thread overview]
Message-ID: <20130630055202.GA16580@brightrain.aerifal.cx> (raw)

Hi all,

With us nearing musl 1.0, there are a lot of things I could use some
help with. Here are a few specific tasks/roles I'm looking for:

1. Put together a list of relevant conferences one or more of us could
   attend in the next 4-6 months. I'm in the US and travelling outside
   the country would probably be prohibitive unless we also find
   funding, but anything in the US is pretty easy for me to get to,
   and other people involved in the project could perhaps attend
   other conferences outside the US.

2. Organize patches from sabotage, musl-cross, musl pkgsrc, etc. into
   suitable form for upstream, and drafting appropriate emails or bug
   reports to send.

3. Check status of musl support with build systems and distros
   possibly adopting it as an option or their main libc. This would
   include OpenWRT, Aboriginal, crosstool-ng, buildroot, Alpine Linux,
   Gentoo, etc. If their people doing the support seem to have gotten
   stuck or need help, offer assistance. Make sure the wiki is kept
   updated with info on other projects using musl we we can send folks
   their way too.

4. Wikimastering. The wiki could use a lot of organizational
   improvement, additional information, and monitoring for outdated
   information that needs to be updated or removed.

5. Rigorous testing. My ideal vision of this role is having somebody
   who takes a look at each bug fix committed and writes test cases
   for the bug and extrapolates tests for possible related bugs that
   haven't yet been found. And who reads the glibc bug tracker so we
   can take advantage of their bug reports too.

Anyone up for volunteering? :-)

Rich


             reply	other threads:[~2013-06-30  5:52 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-30  5:52 Rich Felker [this message]
2013-06-30 10:48 ` Szabolcs Nagy
2013-07-01  3:51   ` Rich Felker
2013-07-01 20:58     ` Szabolcs Nagy
2013-07-01 23:59       ` Rich Felker
2013-07-02  2:19         ` Szabolcs Nagy
2013-07-02  7:49           ` Rich Felker
2013-07-16 16:20             ` Szabolcs Nagy
2013-07-17 15:41               ` Rich Felker
2013-06-30 11:02 ` Daniel Cegiełka
2013-06-30 12:13   ` Rich Felker
2013-06-30 22:29     ` idunham
2013-07-01  3:31       ` Rich Felker
2013-07-01 17:42         ` Isaac
2013-07-01 17:46           ` Alex Caudill
2013-07-01 21:12           ` Isaac
2013-07-01  3:13     ` Rob Landley
2013-07-01  3:43       ` Rich Felker
2013-06-30 15:25 ` Nathan McSween
2013-06-30 22:59   ` Luca Barbato
2013-07-01 11:42 ` LM
2013-07-04 18:05 ` Rob Landley
2013-07-08  7:40   ` Szabolcs Nagy
2013-07-09  2:14     ` Rob Landley
2013-07-09  2:57       ` Matthew Fernandez
2013-07-08 14:45   ` Rich Felker
2013-07-09  2:54     ` Rich Felker
2013-07-08 14:12 ` Anthony G. Basile
2013-07-01 17:44 Felix Janda
2013-07-02  1:08 ` Michael Kerrisk (man-pages)

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=20130630055202.GA16580@brightrain.aerifal.cx \
    --to=dalias@aerifal.cx \
    --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).