From: dams@gentoo.org
To: gentoo-desktop-research@lists.gentoo.org
Cc: seemant@gentoo.org
Subject: Re: [gentoo-desktop-research] Report of the desktop-research meeting.
Date: Thu, 22 Jan 2004 10:28:16 +0100 [thread overview]
Message-ID: <m2n08g72of.fsf@krotkine.idm.fr> (raw)
In-Reply-To: <1074715063.16229.12.camel@sephora> (Seemant Kulleen's message of "Wed, 21 Jan 2004 11:57:43 -0800")
Seemant Kulleen <seemant@gentoo.org> said:
> You know, I have an idea (which isn't mine originally -- the originator
> was the ex-dev ska-fan about 18 months ago, and more recently others
> have mentioned it to me). I think it would be nicer instead of focusing
> on installer, but rather on the desktop experience. One way would be to
> have config tools based on dams' libconf, and the other way would be to
> have UTF-8 default. I think Spider should chime in on this.
you are probably right on the installer part : it's maybe too big for the
-research to develop it. But I think it's still a good thinkg to talk about it,
with logs, meeting reports and so on. It might be good to have at least
organized and written notes on the subject, even if we don't bring anything
new. Installer development should not be held by the -research imo, but
Installer research can be :)
We can discuss the various scenario possible, list them, and see if they are
really doable, realistic, which one is the easiest, or more powerfull, or more
flexible, or more gentoo way. (sorry for my bad english, it's the morning
here:)
The config tools discussion and development will be initiated here. We can end
up with a prototype, and development team(s), schedule, and specifications.
--
dams
--
gentoo-desktop-research@gentoo.org mailing list
next prev parent reply other threads:[~2004-01-22 9:23 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
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 [this message]
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=m2n08g72of.fsf@krotkine.idm.fr \
--to=dams@gentoo.org \
--cc=gentoo-desktop-research@lists.gentoo.org \
--cc=seemant@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