public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Diego Elio Pettenò" <flameeyes@flameeyes.eu>
To: "Diego Elio Pettenò" <flameeyes@flameeyes.eu>,
	"gentoo-dev@lists.gentoo.org" <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Gentoo Hangouts
Date: Mon, 24 Jun 2013 17:21:33 +0100	[thread overview]
Message-ID: <CAHcsgXTDhxdmm64grcL8pTwSp0NGAz_UcHfCQoS2LGh61LuVUg@mail.gmail.com> (raw)
In-Reply-To: <20130624154323.GA101492@skade.schwarzvogel.de>

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

On Mon, Jun 24, 2013 at 4:43 PM, Tobias Klausmann <klausman@gentoo.org>wrote:
>
> It depends how you run it. We have teams having a video thing
> open during the day with there geographically-diverse other team
> members and it works well for them. For those teams, it also
> improves cohesion. Geographically-diverse teams always have to
> actively fight the us-vs-them vibe that seems to be fundamental
> human nature. Aforementioned video link is part of that.
>

Sure, but first of all these are private meetings, and not public ones.
Even more, they are meetings private to the company, and not even with
customers. You can tell that the response to a public vs private meeting is
definitely different. I've witnessed before people trying go show off even
more just because a camera is involved, which can be obnoxious, in my
opinion.


> > And unlike IRC meetings, you can cannot multitask, say making
> > your dinner while discussing this or that feature.
>
> As others have pointed out, this is a double edged sword:
> Sometimes, having less distraction (or getting away with less
> distraction) is a Good Thing.
>

Yeah sure if you can afford it. One thing that people seem to miss is that
Gentoo is _not_ an employment. And while we'd like to keep professional
behaviour, the system of incentives and disincentives that work for an
employment position do not apply to organizations like Gentoo.


>
> > A VC is a full commitment, and its attractiveness is often much
> > higher _before_ you use it..
>
> This does not hold true for me. I'd never used VC before joining
> my current company, and I love it -- iff the alternative is not
> meeting at all or text-only. As I pointed out above, it is
> crucial for team cohesion.
>

Sure and in some ways it's a least worst option. On the other hand you and
I both know that it's not as easy as saying "okay let's all meet at 7" —
timezones, hardware issues, connection issues, you name it. We sidestep
most of these issues as the various problems have been ironed out before..
but to start doing "regular" hangouts between Gentoo teams? It's going to
involve lots of work.


> If you want to have a distincly productive meeting, you need an
> agenda/goals and someone to _run_ the meeeting. But that is true
> of IRC meetings, too.
>
> About the only thing that IRC meetings are invariably better at,
> is logging. Note, however, that logging is no replacment for
> agendas or summarizing the outcome of the meeting.
>

On the other hand, I would be _very_ much against using Hangouts for
anything that involves decision-making or explanation of future planning,
for the very reasons I originally pointed out:

 * they require too much time set aside (I can't even lurk a Hangout if I'm
cooking, or working, or my phone only knows what);
 * they are not for everyone (English is not universal as we'd wish it is —
if it wasn't for last year's experience, I wouldn't want speaking English
in public; William also pointed out another reason);
 * I don't expect a great signal to noise, not only at the beginning but
throughout: try to imagine an unmoderated IRC channel being spoken aloud,
then add a bunch of "can you hear/see me?" from every other participant,
the "what did you say? I can't understand you" and so on so forth.

Honestly, I see as much potential to cause further issues in a team as
there is to solve them.

[-- Attachment #2: Type: text/html, Size: 4556 bytes --]

  reply	other threads:[~2013-06-24 16:21 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ò [this message]
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
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=CAHcsgXTDhxdmm64grcL8pTwSp0NGAz_UcHfCQoS2LGh61LuVUg@mail.gmail.com \
    --to=flameeyes@flameeyes.eu \
    --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