public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Lance Albertson <ramereth@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Gentoo-Status
Date: Tue, 22 Aug 2006 09:45:46 -0500	[thread overview]
Message-ID: <44EB189A.50106@gentoo.org> (raw)
In-Reply-To: <44EB15AD.1040901@gentoo.org>

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

Simon Stelling wrote:
> Lance Albertson wrote:
>> Frankly, the attitude of a lot devs lately towards infra
>> have made many of us not want to communicate what we're doing. If we're
> 
> I can understand that, partly. But that won't help anyone. Assuming
> you're not thinking *nobody* outside infra does respect you, try to
> write the status report for those who you feel respected by. It will
> even make those happy who didn't respect you and maybe even make them
> respect you again because they see that a genuine effort is made to
> solve a problem that buggers them.

I'll see about sending an email in the next few days. Basically, we're
making progress on the bugzie end.

>> not getting respected by you, then why should we respect you back? At
>> least for me personally, I don't hold any personal grudges against
>> anyone unless you stop respecting the group and/or me. Personally, I
>> think the larger problem in Gentoo itself is the attitudes of many
>> developers. Communication aside, it means nothing if we can't deal with
>> each other in a semi-professional manner. It seems like mini-flame
>> explosions on irc/email have happened more frequently in the last few
>> months. This is just going to make the group implode if nothing is done
>> about it.
> 
> Respect is something that should be applied unconditionally, in my
> opinion. The "you don't so I won't" attitude gets us nowhere.
> 

I generally try to do that, but after the 10th time the person doesn't
respect you and demands things from you, its kind of hard to keep that
mentality.

-- 
Lance Albertson <ramereth@gentoo.org>
Gentoo Infrastructure | Operations Manager

---
GPG Public Key:  <http://www.ramereth.net/lance.asc>
Key fingerprint: 0423 92F3 544A 1282 5AB1  4D07 416F A15D 27F4 B742

ramereth/irc.freenode.net


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

  parent reply	other threads:[~2006-08-22 14:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-21 22:56 [gentoo-dev] Gentoo-Status Alec Warner
2006-08-21 23:27 ` Seemant Kulleen
2006-08-22  0:12   ` Joshua Jackson
2006-08-21 23:51 ` Kevin F. Quinn
2006-08-22  0:13   ` Alec Warner
2006-08-22  0:06 ` Ciaran McCreesh
2006-08-22  0:21   ` Alec Warner
2006-08-22  0:27     ` Ciaran McCreesh
2006-08-22 13:20   ` Lance Albertson
2006-08-22 14:33     ` Simon Stelling
2006-08-22 14:40       ` Ciaran McCreesh
2006-08-22 14:45         ` Elfyn McBratney
2006-08-22 14:52           ` Ciaran McCreesh
2006-08-22 14:45       ` Lance Albertson [this message]
2006-08-22 15:10         ` Simon Stelling
2006-08-22 15:17           ` Lance Albertson
2006-08-23 17:18   ` Sune Kloppenborg Jeppesen
2006-08-22  6:09 ` Marius Mauch
2006-08-22 12:57   ` Alec Warner

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=44EB189A.50106@gentoo.org \
    --to=ramereth@gentoo.org \
    --cc=gentoo-dev@lists.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