golubbe

5 ms·

1.
by golubbe 8y ago
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&#
2.
by golubbe 8y ago
"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.
3.
by golubbe 8y ago
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, w
4.
by golubbe 8y ago
Timely discussion in light of today's news from Mongo and recent news from Redis. More restrictive licensing isn't the only answer.
5.
by golubbe 8y ago
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&#x2F
6.
by golubbe 12y ago
We're thrilled to have her. See Marianna's blog post at http://blog.docker.com/2014/11/dockerized-by-marianna-tessel...
7.
by golubbe 12y ago
Docker's blog post on this https://blog.docker.com/2014/09/docker-closes-40m-series-c-l...
8.
by golubbe 12y ago
For a good set of use cases, see https://docker.com/resources/usecases/
9.
by golubbe 12y ago
Details are at docker.io/governance That site also provides a place to submit comments on the proposal itself and nominations for the board.
10.
by golubbe 12y ago
Go to docker.io/governance to see the full proposal (and provide comments/nominations). Our blog explaining the move is at blog.docker.io
11.
by golubbe 13y ago
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 str
12.
by golubbe 13y ago
Interesting post. Looking forward to seeing RelateIQ present on this at the meetup at MongoDB this afternoon.
13.
by golubbe 13y ago
The video is here: http://blog.docker.io/2013/08/docker-hack-day-6-lightning-ta...
14.
by golubbe 13y ago
We're using device-mapper thin provisioning technology. Same copy-on-write capabilities, but more compatible with upstream kernel versions
15.
by golubbe 13y ago
This was an awesome collaboration. Over 15 senior contributors at Red Hat working with us at Docker.
16.
by golubbe 13y ago
Article on Docker. Awesome Alan Kay reference.
17.
by golubbe 13y ago
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 sour
18.
by golubbe 13y ago
What makes this especially exciting for me is that >80% of those people are from the community (i.e. not dotCloud employees).
19.
by golubbe 13y ago
From the author: Thanks to voxoz, Flynn, and Deis for your support .
20.
by golubbe 13y ago
There is a lot of good, introductory material (slideshow, white paper, summary) here: https://www.docker.io/about/
21.
by golubbe 13y ago
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...
22.
by golubbe 13y ago
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/getti
23.
by golubbe 13y ago
Sorry--typo on my part (since corrected). We introduced the approach today, and will make the developer preview available on August 15.
24.
by golubbe 13y ago
Important news for Docker developers. Please let us know what you think.