public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tobias Klausmann <klausman@gentoo.org>
To: "Diego Elio Pettenò" <flameeyes@flameeyes.eu>
Cc: "gentoo-dev@lists.gentoo.org" <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Gentoo Hangouts
Date: Mon, 24 Jun 2013 17:43:23 +0200	[thread overview]
Message-ID: <20130624154323.GA101492@skade.schwarzvogel.de> (raw)
In-Reply-To: <CAHcsgXRSbOoAcGkNeHcecXPyVbsKh44UMF-c=3b7AG=7fAZYhw@mail.gmail.com>

Hi! 

On Mon, 24 Jun 2013, Diego Elio Pettenò wrote:
> I've worked on a VC system most of last year and I now go
> through regular conferences... it's barely okay from a work
> point of view, it takes lots of time to organize so you don't
> want to do that every single day for sure.

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.

> 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.

> 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.

The basic question is: why do you do it? what do you want to get
out of it? If you just want to have a get-together, like going to
the pub together for a few beers, all prep it needs is finding a
time. And beer, maybe.

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.

Regards,
Tobias


  parent reply	other threads:[~2013-06-24 15:43 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 [this message]
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
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=20130624154323.GA101492@skade.schwarzvogel.de \
    --to=klausman@gentoo.org \
    --cc=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