public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: dams@idm.fr
To: Paul de Vrieze <pauldv@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] desktop
Date: Thu, 28 Aug 2003 12:51:15 +0200	[thread overview]
Message-ID: <m2smnm838c.fsf@krotkine.idm.fr> (raw)
In-Reply-To: <200308281225.54022.pauldv@gentoo.org> (Paul de Vrieze's message of "Thu, 28 Aug 2003 12:25:46 +0200")

Paul de Vrieze <pauldv@gentoo.org> said:

> On Thursday 28 August 2003 10:08, dams@gentoo.org wrote:
>> Spider <spider@gentoo.org> said:
>> > begin  quote
>> > On Thu, 28 Aug 2003 00:22:51 +0200
>> >
>> > dams@idm.fr wrote:
>> >> * What is desktop :
>> >> desktop would be the project responsible of the desktop part of gentoo
>> >> Linux, without making global decision, like : should we build a
>> >> special product for desktop, should we have a modified install, should
>> >> we restrict some possibility to default...
>> >
>> > I'm quite against this turn of development as it will split our meager
>> > develpomentteam even further and direct resources at maintaining two
>> > trees in paralell. Even if one is just "desktop cludge" to make the
>> > DesktopDistribution work, it would require Time and Development.
>>
>> Maybe I badly expressed myself, I meant that desktop won't build a
>> special product for desktop, won't ask if we should have a modified
>> install, or if we restrict some possibility to default...
>>
>
> Let me say this about what I view as the responsibilities of -desktop. It has 
> two main responsibilities, the first one is to manage all current desktop 
> packages (delegated to the appropriate subprojects).
>
> The second one is to research (yes research) how the gentoo desktop experience 
> can be improved. That includes things like the menusystem. Some sensible 
> session system (resp. for starting a windowmanager, which is currently quite 
> nonstandard and depending on the display manager (not windowmanager)) and I'm 
> sure there will be enough other things.

The problem is that the conclusion will tend to tune/modify the DE, and it
seems that people here don't want that, they want vanilla DE. For ex., menu
system is the first improvment I think of, but it has a big impact on the
look&feel of the DE. If we don't want DE tuned, then we cannot use debian like
menu system.


>
> That research leads sometimes to proposed changes. Each of these changes will 
> be judged according to a.o. how easy it is to implement them, how standard 
> they are, whether they conform to the gentoo way, etc.

This can be done if we have decided before if we want or not have a gentoo
desktop touch. I don't think it is now decided.

>
> The general idea being that if it is possible everything should just work 
> after the emerge command has been completed. This also might involve changing 
> default configuration files to work with the way things are installed in 
> gentoo (like specifying the correct location of programs). This does however 
> not mean that just anything can be changed in the default configurations. 
> Look and feel should be as standard as possible. (for example k3b should just 
> work out of the box and know allready where cdrecord is installed, etc.)

The last example is not a desktop issue for me. It's the maintainer to do this,
and to ask the cdrecord maintainer informations, if he needs it.


-- 
dams

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-08-28 10:48 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-27 22:22 [gentoo-dev] desktop dams
2003-08-27 22:58 ` Spider
2003-08-28  0:41   ` Brett I. Holcomb
2003-08-28  0:47     ` Jon Portnoy
2003-08-28  0:58       ` Cedric Veilleux
2003-08-28  1:29       ` Riyad Kalla
2003-08-28  1:48       ` Stuart Herbert
2003-08-28  8:08   ` dams
2003-08-28 10:25     ` Paul de Vrieze
2003-08-28 10:51       ` dams [this message]
2003-08-28 11:08         ` Paul de Vrieze
2003-08-28 11:28           ` dams
2003-08-28 13:37             ` Mike Frysinger
2003-08-29  5:22               ` Luke-Jr
2003-08-28 11:15 ` foser
2003-08-28 12:52   ` dams
2003-08-28 13:21     ` foser
2003-08-28 13:51       ` Stuart Herbert
2003-08-28 14:00       ` Paul de Vrieze
2003-08-28 14:10         ` Michael Cummings
2003-08-28 14:34           ` foser
2003-08-28 14:30         ` foser
2003-08-28 17:44         ` Spider
2003-08-28 19:14           ` Peter Ruskin
2003-08-28 19:24             ` foser
2003-08-28 22:07               ` Peter Ruskin
2003-08-28 20:46             ` dams
2003-08-28 21:34               ` Spider
2003-08-28 22:32                 ` foser
2003-08-28 23:01                   ` dams
2003-08-28 20:35           ` dams
2003-08-28 21:03             ` Spider
2003-08-28 21:21               ` dams
2003-08-28 22:40                 ` foser
2003-08-28 21:07           ` Paul de Vrieze
2003-08-28 14:59       ` dams
2003-08-28 21:17         ` Paul de Vrieze
2003-08-28 23:24       ` Jason Stubbs
2003-08-28 13:54     ` Chris Gianelloni
2003-08-28 15:03       ` dams
2003-08-28 15:09         ` Stuart Herbert
2003-08-28 15:36           ` dams
2003-08-28 15:48             ` jonah benton
2003-08-28 14:04   ` Paul de Vrieze
2003-08-28 14:48     ` foser
2003-08-28 23:30       ` Seemant Kulleen
2003-08-29  1:32         ` Luke-Jr
2003-08-29 14:06           ` dams
2003-08-29 14:18             ` Luke-Jr

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=m2smnm838c.fsf@krotkine.idm.fr \
    --to=dams@idm.fr \
    --cc=gentoo-dev@gentoo.org \
    --cc=pauldv@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