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 11:35:51 -0400 [thread overview]
Message-ID: <CAGfcS_=4YOVdFWsLz+7MZcK0OyXfxfrD-+CZSVtKAQ2BZA8hSg@mail.gmail.com> (raw)
In-Reply-To: <1372172964.1496.YahooMailNeo@web120804.mail.ne1.yahoo.com>
On Tue, Jun 25, 2013 at 11:09 AM, Egg Plant <egg.plant@rocketmail.com> wrote:
> The resourcefull developers/users can meet each other at Gentoo Miniconf and
> similar other gatherings in real world. That will make us more human.
I don't think this is really sufficient. As far as I can tell most
people attend such things based on how far they happen to live from
such an event, or whether they have an employer who is willing to pay
for such attendance. It has little to do with resources, unless
you're talking about so much discretionary money that you're literally
willing to spend $1-2k on travel. I certainly am not aware of any
conference that Gentoo has had a substantial presence at within a few
hundred miles of where I live.
I think anything that helps increase interaction among devs is a good
thing. Teams are welcome to organize their meetings in whatever
format works best for them. Gentoo developers are not required to use
IRC at all. Everybody has their favorite medium - some prefer email,
some forums, some IRC, some hangouts/etc, and so on. Some prefer
meeting on weekdays vs weekends, morning vs evening, etc. There are
going to be people inconvenienced or left out no matter what we do.
Sure, some will not be able to participate in Hangouts who could
participate in IRC, but the reverse is true as well.
Rich
next prev parent reply other threads:[~2013-06-25 15: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
2013-06-25 15:09 ` Egg Plant
2013-06-25 15:35 ` Rich Freeman [this message]
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_=4YOVdFWsLz+7MZcK0OyXfxfrD-+CZSVtKAQ2BZA8hSg@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