From: Ben de Groot <yngwin@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] desktop-misc@ needs your help
Date: Mon, 8 Feb 2010 23:52:23 +0100 [thread overview]
Message-ID: <e117dbb91002081452u1b3c8700wbf01fb041d64d88b@mail.gmail.com> (raw)
In-Reply-To: <4B7069D6.3050705@gentoo.org>
I was thinking that maybe we should join the desktop-wm [1] and
desktop-util [2] subprojects and elect one lead, as all herds under
these projects seem to lack manpower and coordination. And we could
try to recruit a few new devs for these herds as well. As I am now a
full-time openbox user, I am willing to redirect some of my activity
to this area.
1: http://www.gentoo.org/proj/en/desktop/wm/index.xml
2: http://www.gentoo.org/proj/en/desktop/util/index.xml
--
Ben de Groot
Gentoo Linux developer (qt, media, lxde, desktop-misc)
______________________________________________________
prev parent reply other threads:[~2010-02-08 22:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-06 17:22 [gentoo-dev] desktop-misc@ needs your help Samuli Suominen
2010-02-07 9:38 ` Markos Chandras
2010-02-08 19:45 ` Krzysiek Pawlik
2010-02-08 22:52 ` Ben de Groot [this message]
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=e117dbb91002081452u1b3c8700wbf01fb041d64d88b@mail.gmail.com \
--to=yngwin@gentoo.org \
--cc=gentoo-dev@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