public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: dams@idm.fr
To: foser <foser@foser.dyn.warande.net>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] desktop
Date: Thu, 28 Aug 2003 14:52:30 +0200	[thread overview]
Message-ID: <m28ype7xm9.fsf@krotkine.idm.fr> (raw)
In-Reply-To: <1062069307.3455.43.camel@rivendell> (foser@foser.dyn.warande.net's message of "Thu, 28 Aug 2003 13:15:07 +0200")

foser <foser@foser.dyn.warande.net> said:


[...]

>
> Thanks for bringing this up again, since this was brought up months ago
> with the creation of the toplevel structure. Although at the time it
> wasn't deemed important enough to be formed at the spot.
>
> I'm all for a toplevel structure to coordinate the desktop efforts,
> although the interference in the projects themselves should be kept to a
> minimum. I see it mostly as a layer to communicate with other teams.

I totally agree with that, you found the words.

>
>> * The gentoo things that would be handeld by the desktop project :
>> X, KDE, gnome, other desktop environment (wmaker, rox, xfce...)
>> *dm (xdm, kdm, gdm, ...)
>
> To sum it up : everything non-console.
>
>> menu system (use gentoo menu system, or get the debian one)
>
> This is part of possible 'tasks' (see down), the whole discussion
> concerning this is still to be started as far as i am concerned.
>
>> * The tasks :
>> - maintain the project component
>
> obvious
>
>> - decide general guidelines to be applied on the desktop project components
>> (do we want DE unification and how much, look and feel, menu entries, default
>> desktop, gentoo control center integration in DE...)
>
> I think the other posts in this thread reflect the general and also my
> sentiments on this perfectly fine. We should keep it as vanilla as
> possible, users know how to work from there.

Maybe add a vanilla flags, that can be unset. When unset, the DE are
preconfigured and gentoo touched.

The pb is that you want vanilla, but you want also some core feature like
centralized menu system, which is not compatible. So either we decide not to
include such features, or to have a flag.

>
>> - write guidelines to be more (free)desktop compliant, to be used by the whole
>> gentoo devs for their packages.
>
> We shouldn't be compliant, we should push upstream developers to be or
> work on their packages being compliant. Us providing some hackish layer
> of compliance is a recipe for disaster. It is fighting symptoms, while
> you should be attacking the problem by its root. I don't see our already
> heavily pressured teams do all sorts of compliance work.
>
> And no, just hiring a few more people is no solution if you want to have
> the same quality/involvement.

That's a possibility, but that means that, as a linux distribution, we don't
provide additional compliance. If you keep the desktop vanilla, we don't either
provide additional desktop default. That can be what we want. But what will
provide gentoo linux, as desktop, then?


[...]

>> desktop may need some other part/project, like some usefull packages (menu),
>> configuration tools, unique control center... That's why we might begin with a
>> representation of what would the perfect desktop product be, and see if we have
>> everything we need in gentoo. If not, then we might suggest the creation of
>> additional projects, or inclusion of needed component.
>
> There is no perfect desktop which you can mold into an ebuild. Gentoo
> already provides the perfect desktop, because users can choose exactly
> what they want from their desktop.

I think a perfect corporate desktop would :

- be cheap
- be installable by not so good technical guys quickly
- be useable at soon as it is installed

Now if the guy has to configure each workstation, it's not very convenient...

-- 
dams

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-08-28 12:49 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
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 [this message]
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=m28ype7xm9.fsf@krotkine.idm.fr \
    --to=dams@idm.fr \
    --cc=foser@foser.dyn.warande.net \
    --cc=gentoo-dev@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