public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan Coutts <dcoutts@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Cc: haskell@gentoo.org
Subject: [gentoo-dev] retirement
Date: Tue, 22 Apr 2008 11:22:14 +0100	[thread overview]
Message-ID: <1208859734.27748.71.camel@localhost> (raw)

Hi folks,

I've decided to retire as a Gentoo dev.

I've been a dev for almost exactly 3 years as part of the Haskell team.
I was team leader for a year or so. I managed to recruit kolmodin a
couple years ago and handed team leadership over to him a few months
ago. It's now his turn to recruit some more people to keep the Haskell
team well staffed.

My decision is based on real world time commitments. I'm in the late
stages of writing up my PhD thesis and I've recently started a Haskell
consultancy company <shameless-plug href="www.well-typed.com"/>. I don't
intend to do much less work packaging but I intend to shift my focus
from Gentoo packaging to the central Haskell packaging infrastructure
http://hackage.haskell.org/. All QA improvements there benefit Gentoo.
I'll still have commit access to the haskell overlay and to the hackport
tool for automatically converting packages hackage->portage. I'll still
be in #gentoo-haskell if you want to find me.

I'd like to thank everyone for being welcoming and friendly and
answering my stupid questions. Thanks especially to the arch teams for
all the time they put in for us in testing and stabilising Haskell
packages on such a wide range of platforms. I feel I should also
apologise to jer for constantly breaking ghc on hppa ;-). Thanks also to
jakub for his work filtering and redirecting bugs to us, along with the
occasional helpful insight.

Best of luck everyone.

-- 
Duncan Coutts : (ex-)Gentoo Developer (Haskell team)

-- 
gentoo-dev@lists.gentoo.org mailing list



             reply	other threads:[~2008-04-22 10:22 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-22 10:22 Duncan Coutts [this message]
2008-04-22 11:02 ` [gentoo-dev] retirement Mike Auty
2008-04-22 18:39 ` Jeroen Roovers
  -- strict thread matches above, loose matches on Subject: below --
2024-06-12 11:55 [gentoo-dev] Retirement Marek Szuba
2011-08-13 18:46 [gentoo-dev] retirement Christopher Brannon
2008-08-10 22:26 [gentoo-dev] Retirement Bo Ørsted Andresen
2008-08-10 22:35 ` Donnie Berkholz
2008-08-11  9:35 ` Santiago M. Mola
2008-08-11 10:58 ` Jorge Manuel B. S. Vicetto
2008-08-10 20:56 Ingmar Vanhassel
2008-08-11  9:36 ` Santiago M. Mola
2008-08-11 10:52 ` Jorge Manuel B. S. Vicetto
2007-05-15  9:58 Anigel
2007-05-15 10:35 ` Petteri Räty
2007-05-15 10:43 ` Wernfried Haas
2006-11-03 19:15 Jon Portnoy
2006-11-03 19:23 ` Wernfried Haas
2006-11-03 19:32 ` Peter Johanson
2006-11-03 19:49 ` Seemant Kulleen
2006-11-03 20:15 ` Josh Saddler
2006-11-03 20:42 ` Paul de Vrieze
2006-11-03 22:23 ` Donnie Berkholz
2006-11-04  8:33 ` Alin Nastac
2006-11-04 22:15 ` Stuart Herbert
2006-11-05 16:04 ` Roy Bamford
2006-11-06 17:17 ` Joshua Jackson
2006-11-12 15:26 ` Jason Huebel
2006-06-08 18:28 Ryan Phillips
2006-06-08 22:58 ` Stuart Herbert

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=1208859734.27748.71.camel@localhost \
    --to=dcoutts@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=haskell@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