[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130630055202.GA16580@brightrain.aerifal.cx>
Date: Sun, 30 Jun 2013 01:52:02 -0400
From: Rich Felker <dalias@...ifal.cx>
To: musl@...ts.openwall.com
Subject: Request for volunteers
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
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
