2. GPL
UTILIZATION
The freedom to run the program, for any purpose (freedom 0)
TAMING
The freedom to change it to make it do what you wish (freedom 1)
DISTRIBUTION
The freedom to redistribute copies so you can help your neighbor (freedom 2)
REDISTRIBUTION
The freedom to distribute copies of your modified versions to others (freedom 3)
3. OPEN SOURCE
COMMUNITY
The idea is, it is everybody's yet it is nobody's
ARCHITECTURE
That allows programs to be extensible
MANY EYES
Any one capable of bringing in change can bring in
ALSO GPL
The driving factor was GPL, which also is GPL
4. CLOUD
ABSTRACTION
The physical resources are hosted under a layer of virtualization
REMOTING
The resources are located in location you do not really know
TENANCY
The resources you own are the resources that you rent
THINNING
The desktop just shrinks in size
5. CLOUD & OPEN SOURCE
CONTROL
Forces people to hand over control of their information to a third party
PROPRIETARY
No one exposes how their Cloud works
LOCKINS
Cloud Services lock you in and governed by major players
PILLARS
Most of the tools on which the Clouds stands are Open Source
6. CLOUD OPEN SOURCE minus
ABSTRACTION
The virtualization platforms that abstract resources are Open Source
REMOTING
The web servers that track down your resources are Open Source
COLLECTIVE
The sharing of resources core to the concept of Open Source
THINNING
For obvious reasons
7. OPEN SOURCE 2.0
FEDERATED
Build on services that are designed to be federated over centralized
OPEN API
APIs that enable services that are not hosted by the API provider
OPEN STANDARDS
One standard to rule all Clouds, no more lockins
PILLARS
Many more tools that will be built around to make cloud better