golubbe

Public alpha also launched today. In addition to reading/commenting on whitepaper, developers can run Storj V3 and view public roadmap and public Jira. Contributing now significantly easier at https://github.com/storj/storj

"Writing a patch is the easiest part of open source. The truly hard stuff is all of the rest: bug trackers, mailing lists, documentation, and other management tasks." Truth.

Cloud computing is becoming the dominant model, and the current combination of OSS licenses and public cloud players/incentives make it nearly impossible for OSS companies to monetize in the cloud. While there are no perfect answers, we either need to come up with new licenses (difficult) or pursue a new approach to cloud (decentralization) that supports OSS monetization.

Timely discussion in light of today's news from Mongo and recent news from Redis. More restrictive licensing isn't the only answer.

To put that $180B in perspective, the TOTAL revenue of the public OSS companies (or those that were public recently before being acquired) is roughly $5B. That includes Red Hat, Mongo, Cloudera, Hortonworks, Elastic, and Mulesoft. If 2/3 of a $180B market is driven by open source, and we want the cycle of innovation to continue, it's in everyone's best interest to find ways to connect open source cloud usage to direct open source monetization.

We're thrilled to have her. See Marianna's blog post at http://blog.docker.com/2014/11/dockerized-by-marianna-tessel...

Docker's blog post on this https://blog.docker.com/2014/09/docker-closes-40m-series-c-l...

For a good set of use cases, see https://docker.com/resources/usecases/

Details are at docker.io/governance That site also provides a place to submit comments on the proposal itself and nominations for the board.

Go to docker.io/governance to see the full proposal (and provide comments/nominations). Our blog explaining the move is at blog.docker.io

This is Ben, the CEO of Docker, and Solomon's partner in crime. Being based on Apache 2.0 (and adopting an open design process, having a large number of non-Docker Inc. maintainers, having over 300 contributors) should be read as a strong signal that we will not go proprietary or even "open core." Anyone can use and modify Docker under Apache 2.0 without fear of "copyleft" or similar restrictions, which creates a strong disincentive for us to abuse our position by going proprietary. Our business plans, as stated in the blog, are around commercial support and hosted services. (In addition, being Apache vs. GPL makes it much easier for enterprises to adopt us, and much easier to get integrated into projects like OpenStack.)

Interesting post. Looking forward to seeing RelateIQ present on this at the meetup at MongoDB this afternoon.

The video is here: http://blog.docker.io/2013/08/docker-hack-day-6-lightning-ta...

We're using device-mapper thin provisioning technology. Same copy-on-write capabilities, but more compatible with upstream kernel versions

This was an awesome collaboration. Over 15 senior contributors at Red Hat working with us at Docker.

Article on Docker. Awesome Alan Kay reference.

This tutorial is a follow up to the interactive docker tutorial at http://www.docker.io/gettingstarted/.

This new tutorial introduces the more advanced topic of Dockerfiles, which automate building containers from source.

What makes this especially exciting for me is that >80% of those people are from the community (i.e. not dotCloud employees).

From the author: Thanks to voxoz, Flynn, and Deis for your support .

There is a lot of good, introductory material (slideshow, white paper, summary) here: https://www.docker.io/about/

We definitely want to see this too, and it is something being investigated for post- 0.8. In the meantime, you may want to read http://kencochrane.net/blog/2013/05/running-docker-on-a-rasp...

Broader compatibility (including reducing kernel dependency) is a major part of this push. There are a number of workarounds today (e.g. patching the kernel, deploying as VM) which are discussed on http://www.docker.io/gettingstarted/ But, obviously, such workarounds aren't practical in every environment.

Sorry--typo on my part (since corrected). We introduced the approach today, and will make the developer preview available on August 15.

Important news for Docker developers. Please let us know what you think.