From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Gentoo Hangouts
Date: Tue, 2 Jul 2013 10:19:53 -0500 [thread overview]
Message-ID: <20130702151953.GB9610@comet.hsd1.mn.comcast.net> (raw)
In-Reply-To: <20130624132108.GA31014@woodpecker.gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1322 bytes --]
On 09:21 Mon 24 Jun , Mike Pagano wrote:
> Sometimes it helps to realize that the people on the other end of the
> wire are just that: people.
>
> I've seen behaviors change among team members for the better.
^^ This.
Seeing people as close to "in person" as we can get without a conference
really does help to improve the quality of our interactions. It's a lot
harder to be a jerk when you can picture the person you're writing to as
a living, breathing person.
Given recent, and more distant, actions by some of our community with
DevRel consequences, it should be clear that treating our fellow
developers decently is a problem. And seriously, hopping on a video chat
once or twice a year should be doable for most of us.
I don't necessarily care a lot about the PR value of any replays, I see
it as much more important to strengthening Gentoo than to do outreach.
That said, I've gotten over 10,000 views of an intro talk on Gentoo
that's posted on YouTube despite its pretty bad audio quality, and
nearly 2,000 views of a Gentoo talk targeted at developers, so there's
clearly people looking for this stuff.
--
Thanks,
Donnie
Donnie Berkholz
Council Member / Sr. Developer, Gentoo Linux <http://dberkholz.com>
Analyst, RedMonk <http://redmonk.com/dberkholz/>
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-07-02 15:20 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 [this message]
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=20130702151953.GB9610@comet.hsd1.mn.comcast.net \
--to=dberkholz@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