public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Egg Plant <egg.plant@rocketmail.com>
To: "gentoo-dev@lists.gentoo.org" <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Re: Gentoo Hangouts
Date: Tue, 25 Jun 2013 08:09:24 -0700 (PDT)	[thread overview]
Message-ID: <1372172964.1496.YahooMailNeo@web120804.mail.ne1.yahoo.com> (raw)
In-Reply-To: <kqc5un$egc$1@ger.gmane.org>



----- Original Message -----
> From: Michael Palimaka <kensington@gentoo.org>
> 
> On 25/06/2013 22:42, Egg Plant wrote:
>>  I don't know whether a new gentoo user like me have any say here, I 
> would like to point out some problems about this proposal !
>> 
>>  2. Gentoo is not backed by any public invested company or private company, 
> no corporation. So there is nobody to show your monthly/quarterly progress, 
> nothing to hide intelligently. That is why I'm here.
>> 
>>  4. More communication channels will just create fragmentation & 
> distraction. Installing & maintaing Gentoo is already a big work, now if I 
> have to check regularly the huge Mailing lists, IRC, Bugzilla, git and now you 
> are saying about Google Hangout, may be later someone will say about Twitter, 
> Facebook, .... I am just finished. It will just waste our time. FYI, I am not a 
> Computer Science student/engineer/researcher.
>> 
>> 
>>    [N.B.: I am neither considering Gentoo because some Hero/Idol said so or 
> helping me out, nor just Stumbleupon it, I am here after trying other distros 
> and lots of associated frustration. ...]
>> 
>>  7. It can be ok if you or somebody else do it as an unofficial effort, 
> don't request the teams to make it another official channel.
>> 
>> 
> 
> These are all good reasons to not use Hangouts. Fortunately, there was 
> nothing in the proposal to suggest that it will be required for anyone, 
> or that it will replace any existing source of information. Therefore 
> anyone who chooses not to make use of Hangouts will not otherwise be 
> affected by them.
>


According to Pavlos Ratis proposal, it will be another channel of communication. I am not protesting to setup an unofficial channel there.

I am fearing that it will gradually become an avenue for talent show, similar to other binary distros. That is why I am against to make it official channel.


Video is more attractive than Text or still photo.

Several developers, who can afford the resources, will gradually shift their communication to that channel. It's somewhat cyclic dependency or chain reaction. It will just increase our workload (of gentoo development awareness). More fragmentation & distraction as well as other technical problems mentioned by others & me.

I don't want any unnecessary attention from some Computer Science students (unable to get a job at Microsoft or Apple!   sorry, I don't like to be that hard) to show their talent and gift me with another unstable, unreliable, expectation only, useless distro.

Change is good, only if it improves our life. For colourfull life there are other things one can play with.

The resourcefull developers/users can meet each other at Gentoo Miniconf and similar other gatherings in real world. That will make us more human.

[P.S.: request you to read my first mail once again, I am not totally against this type of activity. Everything has it's place & time.]
 
===========
I'm yet a learner, warn me if I'm doing any wrong... [|:-)


  parent reply	other threads:[~2013-06-25 15:09 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 [this message]
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=1372172964.1496.YahooMailNeo@web120804.mail.ne1.yahoo.com \
    --to=egg.plant@rocketmail.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