public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Diego Elio Pettenò" <flameeyes@flameeyes.eu>
To: "gentoo-dev@lists.gentoo.org" <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Gentoo Hangouts
Date: Sun, 23 Jun 2013 23:04:14 +0100	[thread overview]
Message-ID: <CAHcsgXSYEwe=gF6umjqnpVjR+VP98PEV66=kat_r1mYgTrr72A@mail.gmail.com> (raw)
In-Reply-To: <CAOgmxWx9Q1a4FJewGp=5pSAjeQekgpLeLTuYaMhbyEqm1-8eGw@mail.gmail.com>

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

Please, let's not try to make this something either mandated or recommended.

I have a personal dislike for video tutorials which tend to take half an
hour to explain something you'd read in ten minutes. Besides, not all of
the developers speak English well enough — heck some people have trouble
writing and understanding written English, let alone spoken.

Honestly, I couldn't get over reading a couple of paragraph here, because
the premise itself is too much to bear for me, sorry.


Diego Elio Pettenò — Flameeyes
flameeyes@flameeyes.eu — http://blog.flameeyes.eu/


On Sun, Jun 23, 2013 at 10:30 PM, Pavlos Ratis <dastergon@gentoo.org> wrote:

> Hello all,
>
> Everyday we talk to each other about different kind of things related
> to Gentoo. IRC and MLs are the primary way of our communication, but
> this is only a text-based communication. I think sometimes it would be
> better to escape from that.
>
> 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.
>
> It's a very interactive way of communication and it helps team bonding. The
> first Hangout of a team would be good to include a short introduction of
> the
> team (what,who,where). Also team members will introduce themselves.
> Then team should start talking about how a user can contribute and
> what is going on in the team. Tips and tricks would be a plus and very
> useful to users. Finally, users will be able to ask
> questions at G+ and then team members will try to answer the most of
> these questions.
>
> Future team meetings could be also held via video hangouts or interviews
> like
> dabbot's doing in his personal blog. In addition, developers
> independent of the team could organize a hangout along with other
> developers to discuss different topics or to have a
> Gentoo-related chit-chat. Users could also participate into this video
> calls.
>
> It's very easy to decide the host of the talk. Maybe the team leads
> would be proper
> for that or someone from the PR. One of the major issues is the
> difference in timezone and the workload of each developer. However, I
> think it would be great to find 1 hour to
> participate. Teams could use a site like http://doodle.com to organize
> the Hangout and find an hour that fit to their schedule.
>
> Except from a camera and a microphone requirement is a Google account and
> www-client/google-talkplugin package which is already in the tree.
>
> It would be great to have teams introduce themselves and inform users in a
> more interactive way how to contribute and answer their questions. Finally
> as
> I said different other topics could be covered in this calls.
>
> All these video calls will be archived to a public Gentoo account in
> Youtube.
>
> I am looking forward to your feedback, your comments and of course for the
> first team that will create a video Hangout!! :)
>
> That's all folks, thanks for your time.
>
> Pavlos
>
>

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

  reply	other threads:[~2013-06-23 22:04 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ò [this message]
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   ` [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='CAHcsgXSYEwe=gF6umjqnpVjR+VP98PEV66=kat_r1mYgTrr72A@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