From: "Avery Pennarun" <apenwarr@gmail.com>
To: "Dmitry Potapov" <dpotapov@gmail.com>
Cc: "Heikki Orsila" <shdl@zakalwe.fi>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Jakub Narebski" <jnareb@gmail.com>,
"Petr Baudis" <pasky@suse.cz>,
msysgit@googlegroups.com, git@vger.kernel.org
Subject: Re: [msysGit] [FYI][PATCH] Customizing the WinGit installer
Date: Mon, 6 Oct 2008 22:40:53 -0400 [thread overview]
Message-ID: <32541b130810061940y4864c420h1a6504b843d4e746@mail.gmail.com> (raw)
In-Reply-To: <20081007015942.GV21650@dpotapov.dyndns.org>
On Mon, Oct 6, 2008 at 9:59 PM, Dmitry Potapov <dpotapov@gmail.com> wrote:
> On Mon, Oct 06, 2008 at 11:11:25PM +0300, Heikki Orsila wrote:
>>
>> I disagree VIOLENTLY with you. I've been utterly struck with this
>> Windows crap here.. I spent a day installing stupid trivial software
>> and answering pointless EULAs. I REALLY REALLY hate extra questions..
>
> Git installer should NOT ask you whether you agree with the license,
> but it merely shows you the license. (At least, it is what was decided
> half a year ago).
FWIW, the only reason *installers* ever show licenses is because they
want to give you *additional* restrictions on top of normal copyright,
and making you "click through" the license before using the
application might (or might not) make those restrictions more legally
enforceable than simply including that license along with the program.
Installers don't show you the license to increase visibility; they do
it for legal reasons.
The most visible place to put a license is in either a splash screen
or a Help|About dialog. If I'm using a program and I want to know the
license, that's where I look.
This whole discussion is silly because end users, who are the ones we
claim to be worried about, will not be the ones running the installer
anyway at a large company. It'll be the IT department guy, who
already knows the license and will have to run the installer 500
times. And if it's not a large company, individuals will see the
license when they go to download the software.
Have fun,
Avery
next prev parent reply other threads:[~2008-10-07 2:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 12:27 [FYI][PATCH] Customizing the WinGit installer Petr Baudis
2008-10-06 14:22 ` [msysGit] " Johannes Schindelin
2008-10-06 14:18 ` Petr Baudis
2008-10-06 15:23 ` Johannes Schindelin
2008-10-06 16:00 ` Jakub Narebski
2008-10-06 16:12 ` Johannes Schindelin
2008-10-06 17:34 ` Linus Torvalds
2008-10-06 17:51 ` Bruce Stephens
2008-10-06 17:54 ` Robin Burchell
2008-10-06 18:01 ` Johannes Schindelin
2008-10-06 19:47 ` [msysGit] " Linus Torvalds
2008-10-07 1:53 ` Dmitry Potapov
2008-10-07 2:10 ` Linus Torvalds
2008-10-07 3:08 ` Dmitry Potapov
2008-10-07 7:46 ` Heikki Orsila
2008-10-07 9:28 ` [msysGit] " Petr Baudis
2008-10-08 7:38 ` Junio C Hamano
2008-10-06 20:11 ` [msysGit] " Heikki Orsila
2008-10-07 1:59 ` Dmitry Potapov
2008-10-07 2:40 ` Avery Pennarun [this message]
2008-10-07 7:42 ` Heikki Orsila
2008-10-06 21:19 ` Abdelrazak Younes
2008-10-06 17:23 ` Petr Baudis
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=32541b130810061940y4864c420h1a6504b843d4e746@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=dpotapov@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=msysgit@googlegroups.com \
--cc=pasky@suse.cz \
--cc=shdl@zakalwe.fi \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).