public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Re: Gentoo Hangouts
Date: Tue, 25 Jun 2013 09:35:39 -0400	[thread overview]
Message-ID: <CAGfcS_m_DpuFOGSbFyFrUwd9DK5tbj_yZxe_xgS0FZ4KL7g+uA@mail.gmail.com> (raw)
In-Reply-To: <kqc5un$egc$1@ger.gmane.org>

On Tue, Jun 25, 2013 at 9:29 AM, Michael Palimaka <kensington@gentoo.org> wrote:
> These are all good reasons to not use Hangouts. Fortunately, there was
> nothing in the proposal to suggest that it will be required for anyone, or
> that it will replace any existing source of information. Therefore anyone
> who chooses not to make use of Hangouts will not otherwise be affected by
> them.

Right now the only "required" forums for communication for developers
are the -core and -dev-announce mailing lists, as far as I'm aware.
Not even IRC is a required communication medium, though obviously that
is where most meetings are held.

My main beef with IRC is that meetings tend to drag on, which is fine
if you're multi-tasking, but not so fine if you have someplace to be
and you'd rather get it done with sooner so that you can get on the
road or whatever (where multitasking isn't exactly safe).  I think
that moving more communication to asynchronous channels might be a
better solution than either Hangouts or IRC, and then using
synchronous channels for things that actually benefit from it (team
building, matters that need some interaction, etc).

Rich


  reply	other threads:[~2013-06-25 13:35 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-23 21:30 [gentoo-dev] Gentoo Hangouts Pavlos Ratis
2013-06-23 22:04 ` Diego Elio Pettenò
2013-06-23 22:21   ` Pavlos Ratis
2013-06-23 22:59     ` Peter Stuge
2013-06-23 22:15 ` Mike Gilbert
2013-06-24  4:52   ` Norman Rieß
2013-06-24  8:14     ` Diego Elio Pettenò
2013-06-24 10:24       ` Pavlos Ratis
2013-06-24 10:42         ` Diego Elio Pettenò
2013-07-04  9:10           ` Peter Stuge
2013-07-05 21:40             ` Raymond Jennings
2013-07-08 15:52               ` Pavlos Ratis
2013-07-17 20:59                 ` Donnie Berkholz
2013-06-24 11:11       ` Rich Freeman
2013-06-24 14:35       ` William Hubbs
2013-06-24 15:43       ` Tobias Klausmann
2013-06-24 16:21         ` Diego Elio Pettenò
2013-06-24  6:31 ` Alexander Berntsen
2013-06-24  9:56   ` Alex Legler
2013-06-24 10:01     ` Chí-Thanh Christopher Nguyễn
2013-06-24 10:22       ` Alex Legler
2013-06-24 10:54 ` [gentoo-dev] " Michael Palimaka
2013-06-24 11:04   ` Markos Chandras
2013-06-24 13:21     ` Mike Pagano
2013-07-02 15:19       ` Donnie Berkholz
2013-06-24 17:10     ` Sven Vermeulen
2013-06-28 23:55       ` Francisco Blas Izquierdo Riera (klondike)
2013-06-25 12:42   ` [gentoo-dev] " Egg Plant
2013-06-25 13:29     ` [gentoo-dev] " Michael Palimaka
2013-06-25 13:35       ` Rich Freeman [this message]
2013-06-25 15:09       ` Egg Plant
2013-06-25 15:35         ` Rich Freeman
2013-06-25 16:04         ` Michael Palimaka
2013-06-26  7:51           ` [gentoo-dev] " Egg Plant
2013-06-26  7:00   ` [gentoo-dev] " Daniel Campbell
2013-06-25 17:57 ` [gentoo-dev] " Roy Bamford
2013-06-25 19:11   ` hasufell

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=CAGfcS_m_DpuFOGSbFyFrUwd9DK5tbj_yZxe_xgS0FZ4KL7g+uA@mail.gmail.com \
    --to=rich0@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