-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Open source + open data = Open cloud
,----[ Quote ]
| The same holds true for Google, Yahoo!, and other Web 2.0 companies. The
| clouds they are creating are closed, though Google has been doing some of the
| right things with open data pledges and increasing commitments to open
| source. (Not everyone is convinced.)
|
| So, users need to be vigilant about keeping themselves from getting entangled
| with cloud lock-in. Demanding open source and open data guarantees are two
| ways. Requiring that the devices we use to access the cloud remain open is
| another way, and one that Tim suggested in his keynote. Preventing the web
| world from being consolidated into the hands of a very few players is another
| way, as Larry Lessig has argued.
`----
http://news.cnet.com/8301-13505_3-10000289-16.html
Recent:
Freedom and privacy in the cloud: a call for action
,----[ Quote ]
| This is a post about freedom. The freedom to keep your data for yourself and
| the freedom to run free software. You should be able to reclaim and enjoy
| these freedoms also when using web applications.
|
| If you are a supporter of the free software movement, you can easily opt for
| Gimp instead of Photoshop, or Firefox instead of Internet Explorer. You can
| also protect the privacy of your data by using the many encryption tools that
| are available (GPG, TrueCrypt, …). But when it comes to web applications
| things get complicated.
|
| [...]
|
| 1. Choose AGPL
|
| Why is AGPL important? Because it means that, if you are an application
| service provider and your services are based on software with an AGPL
| license, you have to make the source code available to anyone that uses the
| service! FSF guidelines suggest to add a “Source” link that leads users to an
| archive of the code right into the web application interface.
`----
http://www.clipperz.com/users/marco/blog/2008/05/30/freedom_and_privacy_cloud_call_action
AGPLv3 Keeps Open Source Vibrant in Age of SaaS
,----[ Quote ]
| For all practical purposes, the AGPLv3 is a key advance for everyone involved
| in open source, regardless of if you are a software developer, Internet end
| user or enterprise end user. The AGPLv3 closes the ASP loophole and keeps the
| freedom of open source software alive, in the age of SaaS and hosted
| applications.
`----
https://fossbazaar.org/?q=content/agplv3-keeps-open-source-vibrant-age-saas
Google pays for Affero ban
,----[ Quote ]
| The projects will join around 10 other AGPL-licensed efforts on SourceForge,
| compared to six on Google Code. Before the defections, Google had been
| discouraging other AGPL projects, saying Google Code does not support AGPL.
|
| The dispute between Google and developers who want to use AGPL - a version of
| GPLv3 tailored for use in software as a service - has rumbled on since last
| November, when AGPL was finalized.
`----
http://www.regdeveloper.co.uk/2008/04/11/google_bans_aero/
Google blocking AGPL in Google Code
,----[ Quote ]
| So, first AGPL was not good enough for Google because it was not
| OSI-approved. That limited its popularity... Now it is OSI-approved. Still,
| it is not popular enough to be accepted in the Google closed open source
| hosting site?
|
| And, by the way, why should people put their open source code in the hands of
| someone who likes open source only when it does good to its business (ehm,
| that could include me, but we are not talking about me, are we ;-) ?
|
| C'mon Chris, give developers the ability of using AGPL for their own projects
| in Google Code. Your fight for no proliferation of licenses is something I
| subscribe to, but AGPL is the license of the future, no matter if Google
| likes it or not. And I can guarantee you it will become even more popular if
| it is accepted in Google Code...
`----
http://www.funambol.com/blog/capo/2008/03/google-blocking-agpl-in-google-code.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkiMKYQACgkQU4xAY3RXLo4c1ACcDZRNAoszom++Xo/g/EGJEKDJ
zN8AmwWsoGF76ToMhXBxwT8KWebEWS8e
=x0FT
-----END PGP SIGNATURE-----
|
|
