public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul de Vrieze <pauldv@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: "m h" <sesquile@gmail.com>
Subject: Re: [gentoo-dev] When will KDE 3.5 be marked as stable?
Date: Tue, 4 Apr 2006 23:05:43 +0200	[thread overview]
Message-ID: <200604042305.43743.pauldv@gentoo.org> (raw)
In-Reply-To: <e36b84ee0604041004p38c54968vec70f9ed1d7eb5bb@mail.gmail.com>

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

On Tuesday 04 April 2006 19:04, m h wrote:
> I'm the OT.  So I apologize to all devs whose precious time I have
> wasted.  This post has probably now consumed about 10x as much time as
> it should've by now.  I totally realize that it is probably super
> annoying to get requests for bumping to stable.  And it wasn't my
> intention at all to put pressure on anyone to bump KDE.   I was only
> curious as to what was holding it up.

You didn't waste time at all. While your question might have been rather 
concise I found it topical enough, and proper. The one wasting our time is 
Stephen P. Becker by behaving a gentoo developer unworthy, and being called 
upon that. He's also forgetting that while one could try asking it at 
gentoo-user, the chances of getting an answer from the developers are very 
thin.

>
> That was my bad for phrasing my question in such a sort manner (not
> following the "howto ask smart questions" protocol).  I figured since,
> I'm seeing posts about 2.6.16 going stable in "2-3 weeks" and
> questions about firefox 1.5, then KDE would be kosher as well (since
> it is arguable on of the most important apps on the linux desktop).
>
> > >> I would like to point out that it was you who flamed me for apparently
> > >> saying RTFM, when in fact if you read my original email, I did nothing
> > >> of the sort.
> > >
> > > You gave a logical RTFM. You're being literal with words when the
> > > meaning of what you said should be fairly clear. You didn't want to
> > > answer the question, so you flamed the person who asked instead of
> > > answering or defering to a more helpful individual.
> >
> > Not really.  I should have actually pointed out that there is no (good)
> > place for such queries originally, but I was doing about 10 things at
> > once, and just sent the typical "don't send offtopic stuff to the
> > gentoo-dev list" reply.  Look back through the archives...this is pretty
> > standard.
> >
> > >> I merely pointed out what should have been clear to anyone
> > >> that signed up for this list, that it is not for whining about arch
> > >> keywording.
> > >
> > > Not everyone is like you. There are all sorts of different people out
> > > there who process information in a lot of different ways. Without a
> > > stated correct place for asking questions about keywording, it wouldn't
> > > be hard to rationalise that the proper place is the dev mailing list.
> >
> > Except that it isn't the proper place.  It is for discussion of
> > technical matters concerning the development of Gentoo.  The closest
> > place that might be sort of on-topic is the gentoo-desktop list, but I
> > generally don't recommend that list because it seems like nobody bothers
> > to answer questions there for the most part.  I think the problem is
> > that the RightPeople(TM) (meaning all the members of the teams for each
> > desktop herd) probably aren't subscribed there.
>
> Sorry I'm not on the desktop list and since I was seeing other posts
> about marking the kernel and firefox as stable, I figured kde fit in
> as well.  My bad.  One solution to naggers like me may be to have
> dedicated per package wiki/homepages where a status is shown (much
> like Trac releases).  Or at least link to pending bugs.  Though I
> realize that this is probably just more overhead for devs who are
> already too busy and would rather just code.
>
> > > You say it should be obvious like it's fact. Not everything is obvious
> > > to everyone--Not everyone is a Steve or Stephanie. They may interpret
> > > conveyed information in different ways and the ambiguity does not help
> > > at all.
> >
> > It should be obvious to anybody who bothered to read the description for
> > this mailing list before signing up.  I can't fix ignorance.
>
> Thanks for the compliment ;)
> "General Gentoo developer discussion mailing list" is the
> description...  I guess my post was not general enough. ;)

You are right, the list is about the development of gentoo. Asking what the 
reasons are why kde is not stabilized yet (while it used to be really fast) 
is totally relevant to that. The list is intentionally not developer only. It 
is a place for the interaction between developers and advanced users on what 
happens in gentoo. It's not for flames ;-).

Paul

-- 
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net

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

  parent reply	other threads:[~2006-04-04 21:11 UTC|newest]

Thread overview: 88+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-03 23:05 [gentoo-dev] When will KDE 3.5 be marked as stable? m h
2006-04-03 23:11 ` Stephen P. Becker
2006-04-03 23:44   ` Aron Griffis
2006-04-04  2:16   ` Kari Hazzard
2006-04-04  2:28     ` Stephen P. Becker
2006-04-04  2:50       ` lnxg33k
2006-04-04  3:23         ` Jason S
2006-04-04  3:37       ` Kari Hazzard
2006-04-04 15:12         ` Stephen P. Becker
2006-04-04 16:11           ` Kari Hazzard
2006-04-04 16:37             ` Stephen P. Becker
2006-04-04 17:04               ` m h
2006-04-04 17:42                 ` Phil Richards
2006-04-04 21:05                 ` Paul de Vrieze [this message]
2006-04-04 21:09               ` Paul de Vrieze
2006-04-04 20:55           ` Paul de Vrieze
2006-04-04 16:42       ` Simon Stelling
2006-04-04 20:52       ` Paul de Vrieze
2006-04-04  2:37     ` Grant Goodyear
2006-04-04 12:05       ` Carsten Lohrke
2006-04-04  9:21   ` Michael Cummings
2006-04-04  9:42     ` Jan Kundrát
2006-04-04 10:38       ` Michael Cummings
2006-04-03 23:13 ` Diego 'Flameeyes' Pettenò
2006-04-03 23:25   ` m h
2006-04-04  5:51     ` [gentoo-dev] " Duncan
2006-04-04  6:16       ` Donnie Berkholz
2006-04-04 10:10         ` [gentoo-dev] " Duncan
2006-04-04  6:09   ` [gentoo-dev] " Philip Webb
2006-04-04  6:42     ` Diego 'Flameeyes' Pettenò
2006-04-04 10:28       ` [gentoo-dev] " Duncan
2006-04-04 12:03       ` [gentoo-dev] " Philip Webb
2006-04-04  9:12   ` Chris Bainbridge
2006-04-04  9:51     ` Diego 'Flameeyes' Pettenò
2006-04-04 10:14     ` [gentoo-dev] " Duncan
2006-04-04 10:38       ` Caleb Tennis
2006-04-04 11:17         ` [gentoo-dev] " Duncan
2006-04-04 12:18         ` [gentoo-dev] " Philip Webb
2006-05-04 11:48           ` [gentoo-dev] " Bart Braem
2006-05-04 12:18             ` Chris Gianelloni
2006-05-04 12:30               ` Jeff Rollin
2006-05-05  7:14               ` Philip Webb
2006-05-05  7:35                 ` Jakub Moc
2006-05-05  7:56                   ` Philip Webb
2006-05-05  8:11                     ` Jakub Moc
2006-05-05  9:03                       ` Michael Kirkland
2006-05-05  8:16                   ` Chris Bainbridge
2006-05-05 20:09                 ` Jeff Smelser
2006-05-06  9:03                 ` Richard Fish
2006-05-04 12:21             ` Jeff Rollin
2006-05-04 13:45               ` Paul de Vrieze
2006-05-04 14:28                 ` Jeff Rollin
2006-05-04 23:29               ` Michael Kirkland
2006-05-05  5:28                 ` Jeff Rollin
2006-05-05 10:30                   ` [gentoo-dev] " Duncan
2006-05-05  6:32                 ` [gentoo-dev] " Kevin F. Quinn (Gentoo)
2006-05-05 11:20                   ` Carsten Lohrke
2006-05-05 13:23                     ` Kevin F. Quinn (Gentoo)
2006-05-05 14:38                       ` Carsten Lohrke
2006-05-05 18:37                         ` Kevin F. Quinn (Gentoo)
2006-05-05 19:10                           ` Carsten Lohrke
2006-05-05 19:08                       ` Chris Gianelloni
2006-05-05  7:20                 ` [gentoo-dev] " Bart Braem
2006-05-05  8:03                   ` Harald van Dijk
2006-05-05  8:33                   ` Donnie Berkholz
2006-05-05  8:43                     ` [gentoo-dev] " Bart Braem
2006-05-05 11:28                       ` Duncan
2006-05-05  8:57                   ` [gentoo-dev] " Patrick Lauer
2006-05-05  9:44                   ` Diego 'Flameeyes' Pettenò
2006-05-06  6:48                     ` Philip Webb
2006-05-06 11:41                       ` Diego 'Flameeyes' Pettenò
2006-05-06 12:48                         ` Philip Webb
2006-05-06 13:01                           ` Jakub Moc
2006-05-06 13:18                         ` [gentoo-dev] " Duncan
2006-05-05 10:50                   ` [gentoo-dev] " Caleb Tennis
2006-05-05 11:27                     ` [gentoo-dev] " Bart Braem
2006-05-05 11:19                   ` [gentoo-dev] " Carsten Lohrke
2006-05-05 11:50                     ` [gentoo-dev] " Bart Braem
2006-05-06  9:28                     ` [gentoo-dev] " Richard Fish
2006-05-05  7:37                 ` [gentoo-dev] " Philip Webb
2006-05-05 11:00                   ` [gentoo-dev] " Duncan
2006-05-05 21:52                   ` [gentoo-dev] " Jan Kundrát
2006-05-05 12:03                 ` Marius Mauch
2006-05-04 13:05             ` Duncan
2006-05-04 13:47               ` Guillaume Pujol
2006-05-06  8:56             ` Richard Fish
2006-04-04 11:50     ` [gentoo-dev] " Carsten Lohrke
2006-04-08 13:41 ` Wernfried Haas

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=200604042305.43743.pauldv@gentoo.org \
    --to=pauldv@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=sesquile@gmail.com \
    /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