From: foser <foser@gentoo.org>
To: gentoo-desktop-research@lists.gentoo.org
Subject: Re: [gentoo-desktop-research] Report of the desktop-research meeting.
Date: Tue, 20 Jan 2004 11:40:05 +0100 [thread overview]
Message-ID: <1074595204.13623.27.camel@rivendell> (raw)
In-Reply-To: <200401200954.58818.pauldv@gentoo.org>
On Tue, 2004-01-20 at 09:54, Paul de Vrieze wrote:
> The report of yesterday's desktop-research meeting can be found at:
> http://www.gentoo.org/proj/en/desktop/research/meeting_reports.xml#doc_chap2
It lacks any rationale or even if what i proposed got discussed, which i
think is of more immediate importance than any of both currently started
subprojects. An IRC log would be helpful or even better a short summary.
In the subprojects themselves i lack both rationale and any serious
details of how this is going to be planned. To be honest the 'graphical
installer' is proposed and started seven times seven times by now
without any significant results. And i doubt it falls under the category
'desktop project', it's much broader and has actually little to do with
working on a desktop. On a minor note, the lead is not even member of
the research project (or not so on the project page) and that seems like
a logical requirement to me. Is it even a good idea to have a DTL lead
also lead a research project? DTL leads should be validating their
personally lead projects in the end, that's not a good thing per se.
Just member would probably be better.
Now let's get back to my hack 'n slash game ;)
- foser
--
gentoo-desktop-research@gentoo.org mailing list
next prev parent reply other threads:[~2004-01-20 10:40 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 8:54 [gentoo-desktop-research] Report of the desktop-research meeting Paul de Vrieze
2004-01-20 9:12 ` Mario Udina
2004-01-20 10:11 ` Paul de Vrieze
2004-01-20 10:40 ` foser [this message]
2004-01-20 10:48 ` Tiemo Kieft
2004-01-20 12:23 ` Donnie Berkholz
2004-01-20 13:47 ` foser
2004-01-20 14:21 ` Donnie Berkholz
2004-01-20 17:53 ` Brandon Hale
2004-01-20 19:33 ` dams
2004-01-20 19:36 ` dams
2004-01-21 0:07 ` foser
2004-01-20 19:39 ` Joe McCann
2004-01-21 10:06 ` dams
2004-01-20 12:55 ` Paul de Vrieze
2004-01-20 14:00 ` foser
2004-01-20 17:30 ` Tom Hosiawa
2004-01-21 19:57 ` Seemant Kulleen
2004-01-21 20:01 ` Donnie Berkholz
2004-01-21 22:58 ` foser
2004-01-22 0:13 ` Alastair Tse
2004-01-22 9:11 ` dams
2004-01-22 9:25 ` dams
2004-01-22 9:28 ` dams
2004-01-22 17:02 ` [gentoo-desktop-research] Installer Donnie Berkholz
2004-01-22 17:47 ` Tiemo Kieft
2004-01-22 20:45 ` Paul de Vrieze
2004-01-22 18:38 ` Scott Koch
2004-01-23 0:07 ` Tiemo Kieft
2004-01-23 15:57 ` foser
2004-01-23 17:18 ` dams
2004-01-23 19:14 ` [gentoo-desktop-research] Installer's Target user group Scott Koch
2004-01-24 0:47 ` foser
2004-01-23 20:18 ` Scott Koch
2004-01-24 14:55 ` foser
2004-01-25 0:07 ` Nathaniel McCallum
2004-01-24 19:19 ` Tom Hosiawa
2004-01-25 0:29 ` lukas
2004-01-25 1:00 ` Nathaniel McCallum
2004-01-25 1:12 ` lukas
2004-01-24 1:26 ` Steve Barnhart
2004-01-24 15:04 ` foser
2004-01-24 10:45 ` Paul de Vrieze
2004-01-24 14:50 ` foser
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=1074595204.13623.27.camel@rivendell \
--to=foser@gentoo.org \
--cc=gentoo-desktop-research@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