From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: dev-portage@gentoo.org
Subject: Re: [gentoo-dev] Gentoo-Status
Date: Tue, 22 Aug 2006 08:57:10 -0400 [thread overview]
Message-ID: <44EAFF26.5040205@gentoo.org> (raw)
In-Reply-To: <20060822080950.012ff1e2@sven.genone.homeip.net>
Marius Mauch wrote:
> On Mon, 21 Aug 2006 18:56:11 -0400
> Alec Warner <antarus@gentoo.org> wrote:
>
>> It has been noted that certain projects do not communicate their
>> activities well.
>>
>> Many projects provide documentation for things(java), provide status
>> updates on things(ppc), have bits in the gwn (x86,userrel,amd64),
>> Release releases (releng), or have active webpages (adopt-a-dev,
>> bugday)
>>
>> There are some projects that keep to themselves; AND these projects
>> concern other projects (are global, to an extent). This AND means I
>> can leave out things like arch teams, or smaller projects that don't
>> update often. This mail is not meant for things like that. So below
>> we have 3 large far-reaching projects.
>>
>> Gentoo Quality Assurance Team
>> Gentoo Infrastructure Team
>> Gentoo Portage Team
>> Gentoo Foundation
>> Gentoo Council
>>
>> All 5 of these projects are active. However all 5 have failed to
>> communicate what they are doing; leading to people asking multiple
>> times about an issue, people getting frustrated, people getting
>> outright pissed off and hostile. Today especially has been a bad day
>> for this.
>
> If this really concerns you then I have to ask why *you* didn't send
> status reports for the Portage Team in the past?
>
> Marius
>
Actually the Portage Team's lack of communication was brought to my
attention recently by Tsunam after a lengthy discussion on irc. I was
on the team, I certainly knew what was going on ;) Same with QA. Same
with (mostly) infra since I hang out in -infra all day long. But as it
has been noted in the past that not everyone can hang in every channel
and "get a feel for what is going on" I figured I would volunteer to
relay information.
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2006-08-22 12:59 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
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 [this message]
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=44EAFF26.5040205@gentoo.org \
--to=antarus@gentoo.org \
--cc=dev-portage@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