public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: dilfridge@gentoo.org
Subject: Re: [gentoo-dev] Gentoostats, SoC 2011
Date: Thu, 25 Aug 2011 10:33:15 +0200	[thread overview]
Message-ID: <20110825103315.5ad4f12d@pomiocik.lan> (raw)
In-Reply-To: <201108241303.45073.dilfridge@gentoo.org>

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

On Wed, 24 Aug 2011 13:03:44 +0200
"Andreas K. Huettel" <dilfridge@gentoo.org> wrote:

> Am Mittwoch 24 August 2011, 12:48:35 schrieb Patrick Lauer:
> > 
> > If you sneakily add something to cron.daily by default you can get
> > pretty nice coverage. But I guess anyone trying that in Gentooland
> > will meet some rather unpleasant resistance :)
> > 
> 
> Of course, we could place it in some blatantly obvious way into a
> default configuration, together with a big fat message what it does
> and how to quickly disable it. 
> 
> We'd get better coverage in an opt-out system than in an opt-in
> system.

And a larger number of angry users which missed the warning and now
have to pay for additional GPRS transfer or so. And when people use
GPRS rarely, they usually don't think about random apps that use
the connection in background.

> (First idea- package is pulled in by a default-on useflag and
> installs itself into cron.daily. BEFORE it runs the first time it
> outputs said message and asks for permission to proceed (which cannot
> be done in the cron job obviously but we'd find a way).)

And what if it can't ask for that? Assuming you're talking about
'opt-out', I guess the fallback would be to 'yes'. We don't want to end
up like Windows, where you get AFK for five minutes and then discover
the system has rebooted.

-- 
Best regards,
Michał Górny

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 316 bytes --]

  parent reply	other threads:[~2011-08-25  8:32 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-22 21:20 [gentoo-dev] Gentoostats, SoC 2011 Vikraman
2011-08-23 16:16 ` Andreas K. Huettel
2011-08-24 10:31   ` Thomas Kahle
2011-08-24 10:48     ` Patrick Lauer
2011-08-24 11:03       ` Andreas K. Huettel
2011-08-24 11:45         ` Thomas Kahle
2011-08-24 11:59           ` Mario Fetka
2011-08-24 12:05           ` Rich Freeman
2011-08-24 14:47             ` Alec Warner
2011-08-25  8:33         ` Michał Górny [this message]
2011-08-24 11:07       ` Rich Freeman
2011-08-24 13:03         ` [gentoo-dev] " Duncan
2011-08-24 11:13       ` [gentoo-dev] " Thomas Kahle
2011-08-25 10:42       ` [gentoo-dev] " Nikos Chantziaras
2011-08-25 12:43         ` Markos Chandras
2011-08-25 14:15           ` Patrick Nagel
2011-08-25 14:48             ` Fabian Groffen
2011-08-25 10:48       ` [gentoo-dev] " Roy Bamford
2011-08-25 12:20         ` Rich Freeman
2011-08-25 14:35           ` Alec Warner
2011-08-25 14:49             ` Rich Freeman
2011-08-26  3:18             ` Jorge Manuel B. S. Vicetto
2011-08-26  9:04               ` Dale
2011-08-29 21:23               ` Donnie Berkholz
2011-08-30  1:53                 ` Jorge Manuel B. S. Vicetto
2011-08-30  2:11                   ` Matt Turner
2012-04-27 17:34 ` [gentoo-dev] " Nikos Chantziaras
2012-04-27 18:42   ` Alec Warner
2012-04-28 19:28   ` G. Gaydarov

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=20110825103315.5ad4f12d@pomiocik.lan \
    --to=mgorny@gentoo.org \
    --cc=dilfridge@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