From: Denis Dupeyron <calchan@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: gentoo-dev-announce@lists.gentoo.org
Subject: [gentoo-dev-announce] New developer: Andrey Kislyuk (weaver)
Date: Wed, 28 May 2008 11:30:36 +0200 [thread overview]
Message-ID: <1211967041.4481.34.camel@zaphod> (raw)
It's my pleasure to introduce Andrey Kislyuk (weaver) as a new Gentoo
developer. He has a long experience working in the science overlay, and
thus will join the Science project lead by his mentor, George
Shapovalov.
Andrey is originally from Sochi, Russia, but now lives in San Ramon,
California, and considers it home. He is a graduate student in
bioinformatics. In his spare time he enjoys running, biking, martial
arts, computer games and spending time with his friends.
At work Andrey uses a variety of bioinformatics software on various
computers, including HPC clusters. He also has experience with perl, C,
C++, Java and shell scripting.
Andrey was already kicked^Wintroduced on irc some time ago. This delayed
announcement is merely a byproduct of procrastination and too much time
spent in airports. Blame me.
Please everybody, give weaver a warm welcome.
Denis.
--
gentoo-dev-announce@lists.gentoo.org mailing list
reply other threads:[~2008-05-28 16:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1211967041.4481.34.camel@zaphod \
--to=calchan@gentoo.org \
--cc=gentoo-dev-announce@lists.gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
/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