mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rob Landley <rob@landley.net>
To: musl@lists.openwall.com
Cc: musl@lists.openwall.com
Subject: Re: Request for volunteers
Date: Thu, 04 Jul 2013 13:05:06 -0500	[thread overview]
Message-ID: <1372961106.6645.3@driftwood> (raw)
In-Reply-To: <20130630055202.GA16580@brightrain.aerifal.cx> (from dalias@aerifal.cx on Sun Jun 30 00:52:02 2013)

On 06/30/2013 12:52:02 AM, Rich Felker wrote:
> 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.

CELF turned into the "Linux Foundation Embedded Linux Conference" and  
they squished it together with some Android thing. I've never been to  
the Plumber's conference half my twitter list seems to go.

Ohio LinuxFest's call for papers is open until Monday:

---

Sender: news.olf@gmail.com
Received: by 10.223.36.69 with HTTP; Thu, 27 Jun 2013 07:03:14 -0700  
(PDT)
Date: Thu, 27 Jun 2013 10:03:14 -0400
Message-ID:  
<CAJtFCaq7J9v3QfjCZ+tRD2-zna_Y5J5FrmJ-gEZ_mGRFSUgUJQ@mail.gmail.com>
Subject: Oho LinuxFest Call for Talks closing soon
From: Kevin O'Brien <news@ohiolinux.org>

Hello, we are asking for a little help from you in getting the word out
that the Ohio LinuxFest Call for Talks will be closing 7/8/13. Obviously
the more proposals we get the better the program we can put together,  
so we
are asking if you could help us out by posting something to your  
followers
on places like Facebook, Google+, LinkedIn, Twitter, and Identi.ca (or  
any
other social media you like). The page with the submission is
https://ohiolinux.org/cfp.

Thanks for any help you can give us.

--
Kevin O'Brien
Publicity Director, Ohio LinuxFest
news@ohiolinux.org
https://ohiolinux.org

> 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.

Is the Linux Test Project relevant?

Rob

  parent reply	other threads:[~2013-07-04 18:05 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-30  5:52 Rich Felker
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 [this message]
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=1372961106.6645.3@driftwood \
    --to=rob@landley.net \
    --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).