unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Thomas Lord <lord@emf.net>
Cc: julien@danjou.info, emacs-devel@gnu.org,
	carsten.dominik@gmail.com, rms@gnu.org, dave@lab6.com
Subject: Re: Google modules integration
Date: Tue, 14 Sep 2010 21:38:59 +0900	[thread overview]
Message-ID: <87zkvkzeho.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <1284404822.3329.135.camel@dell-desktop.example.com>

Thomas Lord writes:

 > They would rather leverage their raw data to attack
 > software freedom as pertains to maps (much as they
 > attack software freedom as pertains to search).

I see no (necessary) attack on *software* freedom here.  They're
simply keeping the *data* secret.

"Simple" of course does not mean "good".  It just means that there is
nothing runnable here for the user to study, modify, or redistribute.
Google could quite possibly freely distribute all the software used,
and still maintain a profitable monopoly over the data.  (More likely,
they do have substantial proprietary software involved in the
databases and image generation -- but OTOH they probably want
everything in the Maps API to be free software.)

That's why I think it is a mistake to distinguish between software and
other information (as the Free Documentation License does, for
example).



  parent reply	other threads:[~2010-09-14 12:38 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-09 20:23 Google modules integration Julien Danjou
2010-09-09 22:25 ` Stefan Monnier
2010-09-09 22:56   ` Lennart Borgman
2010-09-09 23:36     ` Ted Zlatanov
2010-09-09 23:43     ` Jambunathan K
2010-09-10  6:36       ` Glenn Morris
2010-09-11  5:29         ` Richard Stallman
2010-09-12  0:36           ` Glenn Morris
2010-09-12  1:42             ` Juanma Barranquero
2010-09-12  2:29               ` Óscar Fuentes
2010-09-12  9:34               ` Jambunathan K
2010-09-12 10:12                 ` Jeff Clough
2010-09-13  2:07                   ` Richard Stallman
2010-09-12 17:27               ` Stephen J. Turnbull
2010-09-13  7:18                 ` Richard Stallman
2010-09-12 11:24             ` Richard Stallman
2010-09-12 18:35               ` Glenn Morris
2010-09-13  7:18                 ` Richard Stallman
2010-09-13 16:22                   ` Jambunathan K
2010-09-14  8:16                     ` Richard Stallman
2010-09-10  6:29     ` Julien Danjou
2010-09-10  6:43       ` Glenn Morris
2010-09-11  5:29       ` Richard Stallman
2010-09-11 12:28         ` Stefan Monnier
2010-09-12 11:23           ` Richard Stallman
2010-09-09 23:33   ` Sebastian Rose
2010-09-10  6:17   ` Julien Danjou
2010-09-10  8:30     ` Andreas Schwab
2010-09-10 11:00     ` Stefan Monnier
2010-09-11  5:30       ` Richard Stallman
2010-09-10  8:08 ` Andy Wingo
2010-09-10 11:26   ` Thierry Volpiatto
2010-09-13 14:36   ` James Cloos
2010-09-10 15:42 ` Richard Stallman
2010-09-10 17:47   ` Thomas Lord
2010-09-10 18:03     ` Chad Brown
2010-09-10 18:10       ` Thomas Lord
2010-09-11 15:50         ` Richard Stallman
2010-09-10 19:07       ` Sebastian Rose
2010-09-11 15:49         ` Richard Stallman
2010-09-11 20:03           ` Sebastian Rose
2010-09-11 15:50     ` Richard Stallman
2010-09-13 19:07       ` Thomas Lord
2010-09-13 19:09         ` Thomas Lord
2010-09-15  2:39           ` Richard Stallman
2010-09-14 12:38         ` Stephen J. Turnbull [this message]
2010-09-15  2:39         ` Richard Stallman
2010-09-11  5:38   ` Stephen J. Turnbull
2010-09-12 11:24     ` Richard Stallman
2010-09-12 17:21       ` Stephen J. Turnbull
2010-09-20  0:16         ` Richard Stallman
2010-09-21  5:40           ` Stephen J. Turnbull
2010-09-19  9:34 ` Julien Danjou
2010-09-21 16:01   ` Chong Yidong
2010-09-21 16:30     ` Julien Danjou
2010-09-21 16:50       ` Chong Yidong
2010-09-21 17:24         ` Thierry Volpiatto
2010-09-21 17:25       ` Sebastian Rose

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zkvkzeho.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=carsten.dominik@gmail.com \
    --cc=dave@lab6.com \
    --cc=emacs-devel@gnu.org \
    --cc=julien@danjou.info \
    --cc=lord@emf.net \
    --cc=rms@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).