public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Campbell <dlcampbell@gmx.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Gentoo Hangouts
Date: Wed, 26 Jun 2013 02:00:48 -0500	[thread overview]
Message-ID: <51CA91A0.5090108@gmx.com> (raw)
In-Reply-To: <kq98h2$kmq$1@ger.gmane.org>

On 06/24/2013 05:54 AM, Michael Palimaka wrote:
> On 24/06/2013 07:30, Pavlos Ratis wrote:
>> That's why I'd like to propose Gentoo Hangouts. Gentoo Hangouts will
>> be Google+  video Hangouts(video calls) held by teams or developers
>> independent of a team. The main goal is to have the teams introduce
>> themselves and discuss about different issues in their Gentoo-related
>> projects.
> 
> Thanks for taking the time and initiative to work on something new, I am
> sure it will prove interesting.
> 
> It is the response that confuses me - I don't understand why everyone is
> rushing to shut it down before it even begins. For those that are not
> interested in the idea of a video hangout, just don't use it and move on
> - simple.
> 

I'm a user (and would-be dev) and don't like the idea of relying on
anything related to Google or another outside entity for devs and/or
users to communicate. The software is also non-free and closed source.

It's true that people can "just move on", but that strikes me as an
attempt to ward off criticism and not work at solving the perceived
problem: "how do we get richer communication between Gentoo devs/users?"

Mumble exists for voice chat... certainly there's a FOSS video chat
option somewhere? Diego's points wrt time management and multitasking
are also salient.


  parent reply	other threads:[~2013-06-26  7:01 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
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   ` Daniel Campbell [this message]
2013-06-25 17:57 ` 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=51CA91A0.5090108@gmx.com \
    --to=dlcampbell@gmx.com \
    --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