public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Seemant Kulleen <seemant@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] desktop
Date: Thu, 28 Aug 2003 16:30:43 -0700	[thread overview]
Message-ID: <20030828163043.0375ef96.seemant@gentoo.org> (raw)
In-Reply-To: <1062082102.3455.150.camel@rivendell>

[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]

Perhaps Damien came off wrong initially, but please people cut him some
slack.  Things have gotten a little personal in the argument.  I think
it's better to keep the discussion focused on the initial concerns, viz.
what exactly makes up a Desktop TLP and why.  I would tend to think that
the TLP would be non-intrusive to the individual projects involved, ie
gnome, kde, commonbox, xfce4, e, and so on.  I think dams is only trying
to make it, on the whole, more co-ordinated, with the aim of improving
communication across them and across to other projects (like the lower
level libs and what-not).

Additionally, Paul mentioned the kde herd being a little too all
encompassing, which is a separate issue -- but it is entirely up to him
and the kde@gentoo.org people to create the sub-herds as they see fit.

Thanks,


-- 
Seemant Kulleen
Developer and Project Co-ordinator,
Gentoo Linux					http://dev.gentoo.org/~seemant

Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x3458780E
Key fingerprint = 23A9 7CB5 9BBB 4F8D 549B 6593 EDA2 65D8 3458 780E

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-08-28 23:31 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
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 [this message]
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=20030828163043.0375ef96.seemant@gentoo.org \
    --to=seemant@gentoo.org \
    --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