From: Michael Palimaka <kensington@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Gentoo Hangouts
Date: Tue, 25 Jun 2013 23:29:01 +1000 [thread overview]
Message-ID: <kqc5un$egc$1@ger.gmane.org> (raw)
In-Reply-To: <1372164171.99503.YahooMailNeo@web120802.mail.ne1.yahoo.com>
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 !
>
> 1. Video requires high bandwidth internet, so useless in developing countries, where even today you can not think of 24x7 internet. Yes, there are Broadband, 3G, 4G, ... just as advertisement, no real speed or reliability, or you may say we can not bear the huge cost.
>
>
> 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.
>
> 3. I am subscribed to almost all mailing lists (I think it's justified for a newcomer), so already getting huge mails. There is IRC for realtime communication, which is easily configurable in any computing device, no big price, no hidden code (atleast for the client), no high bandwidth network, no battery drain.
>
> 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.: Gentoo is different from other distros, every user need to be half developer/tester here. It's not as polished/finished as the binary distros (atleast what they want to be). It provides choice, ultimate customization, which is not a child play. Users like to be aware of what is cooking with the ebuilds & sourcecode, what will eventually come within a couple of months to their stable system, unlike 6 months of testing interval in binary distros.]
>
> 5. I do'nt know whether people outside of UK, USA, Australia, Canada, Germany and elites of India, South Africa are at all comfortable with spoken english, I mean to speak. So language will be a big barrier for this type of your promotional activity.
>
> [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. Distrowatch is there to maintain the Linux Distro Stock Exchange.]
>
> 6. other members already stated some other valid reasons against it, I'm not repeating.
>
> 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.
>
> 8. For promotional activities, I would like to have an YouTube/<AnyPopularSite> channel on getting started type video tutorial, or developer's interview etc, specially during new Live DVD releases, Gentoo birthday, 25th December (people will have one week to play with Gentoo). If possible, make it multilingual or atleast provide multilingual subtitle.
>
> 9. On a different note, I would like to have the Handbook split into different parts: 1. Getting started (installation in Qemu/Virtualbox preferably), 2. Advanced Network configuration, 3. Software Management in details, 4. System/Service management (OpenRC, Systemd). The big book for a newcomer is toooo boring.
> I know it's not the right place, just a comment for now!
>
>
> ===========
> I'm yet a learner, warn me if I'm doing any wrong... [|:-)
>
>
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.
next prev parent reply other threads:[~2013-06-25 13:29 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 ` Michael Palimaka [this message]
2013-06-25 13:35 ` [gentoo-dev] " 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='kqc5un$egc$1@ger.gmane.org' \
--to=kensington@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