public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mikael Hallendal <hallski@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] ebuilds for kde3 beta etc.
Date: 26 Dec 2001 04:01:25 +0100	[thread overview]
Message-ID: <1009335686.8878.8.camel@zoidberg> (raw)
In-Reply-To: <20011225204438.A17475@chiba.3jane.net>

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

ons 2001-12-26 klockan 03.44 skrev Daniel Robbins:

> Hallski, how many times in the past have I said "I'm giving Hallski the final
> decision on this one"?  I hope you'll agree it's been quite a few times.  In
> these times, the final decision has been given to you because I trust your
> expertise.  You have been given authority over the desktop aspects of Gentoo
> Linux, but branching CVS is something that affects more than just Desktop
> developers.  You should not be surprised that, in this particular case, I
> exerted my authority and made this decision.  It's certainly within my "job
> description" to make this decision.  And not to be rude, but whether or not to
> branch CVS is really not your decision.

I've never claimed branching the CVS is my decision. I posted is as a
solution to this problem. Wether putting beta KDE packages in Portage
should be my descision (if I've not been incorrectly informed about my
role in Gentoo). Since in the end I'm responsible for desktop issues,
even though Dan is currently responsible for KDE stuff.

> > Also, the "rm -rf /" example misses the point. The point is that if we have
> > lots of beta-stuff in Portage (available to the users) we'll end up spending
> > loads of hours supporting it (no matter how many signs of "Unsupported" we
> > write).
> 
> The "rm -rf /" example is exactly the point.  Inform the user, and let *them*
> make an *educated* decision.  I trust the Gentoo Linux user base; we're not
> designing a distribution for monkeys here.  Taking control away from users is
> really not part of the Gentoo Linux philosophy.

I'm all for users being able to try out new stuff. And what I meant
about it's not the point is that if the user does "rm -rf /" he won't
come to us for support. If a user (after installing KDE3) notices bad
behaviour in various places it might take a very long time tracking it
back to KDE (thus spending lots of developer time).

Also, even _if_ users read the warnings and is willing to take the risk
it will end up taking lots of our time.

If we on the other hand say that we don't have much user support and
leave it at that it's all fine by me. But then this should be made
clear.

So, I'd say this particular issue is in the end my descission, wether or
not to branch the entire portage is _not_ my descision (alone), but I'd
say I should have a say in the matter. But that is out of the scoop for
this discussion.

Regards,
  Mikael Hallendal

-- 

Mikael Hallendal
Gentoo Linux Developer, Desktop Team Leader
CodeFactory AB, Stockholm, Sweden


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

  reply	other threads:[~2001-12-26  3:01 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-22 16:57 [gentoo-dev] ebuilds for kde3 beta etc Dan Armak
2001-12-22 17:28 ` Daniel Robbins
2001-12-22 18:00   ` Dan Armak
2001-12-22 18:29     ` Guido Bakker
2001-12-22 18:12       ` Dan Armak
2001-12-23 13:44         ` Mikael Hallendal
2001-12-23 14:07           ` Dan Armak
2001-12-23 23:08             ` Mikael Hallendal
2001-12-24  0:36               ` Daniel Robbins
2001-12-24  8:27               ` Geert Bevin
2001-12-25  1:12                 ` Mikael Hallendal
2001-12-25  5:00                   ` Dan Armak
2001-12-25  5:11                     ` Daniel Robbins
2001-12-25 12:10                       ` Mikael Hallendal
2001-12-25 15:49                         ` Daniel Robbins
2001-12-25 20:19                           ` Mikael Hallendal
2001-12-25 20:40                             ` Geert Bevin
2001-12-26  1:47                               ` Daniel Robbins
2001-12-26  2:14                                 ` Mikael Hallendal
2001-12-26  2:44                                   ` Daniel Robbins
2001-12-26  3:01                                     ` Mikael Hallendal [this message]
2001-12-26  3:33                                       ` Daniel Robbins
2001-12-26  4:10                                         ` Mikael Hallendal
2001-12-26  5:43                                           ` Daniel Robbins
2001-12-26  6:39                                             ` Dan Armak
2001-12-26  6:51                                               ` Mikael Hallendal
2001-12-26  6:56                                                 ` Joshua Pierre
2001-12-27 19:41                                               ` Damon M. Conway
2001-12-26  5:16                               ` Joshua Pierre
2001-12-26  1:51                             ` Daniel Robbins
2001-12-24  9:59               ` Guido Bakker
2001-12-24 12:11                 ` Sebastian Werner
2001-12-24 13:38                   ` Dan Armak
2001-12-25  1:14                   ` Mikael Hallendal
2001-12-23 14:13   ` Dan Armak
2001-12-26  9:34     ` Dan Armak
2001-12-26  9:37     ` Dan Armak
2001-12-26 13:46       ` Bart Verwilst
2001-12-26 16:50         ` Daniel Robbins

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=1009335686.8878.8.camel@zoidberg \
    --to=hallski@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