Live data from Hacker News

A new upstream project to break up Docker into independent components

github.com

21–30 of 321 posts

Re: A new upstream project to break up Docker into independent components

#21
post #5

More information can be found there: https://github.com/moby/moby/pull/32691 > Docker is transitioning all of its open source collaborations to the Moby project going forward. Should I understand that the core team wants to keep the brand "Docker" but use it in a commercial way, while Moby will be the underlying open source code? Is it Docker/Moby = RHEL/Fedora ? or Docker/Moby = Mongodb.com/Mongodb.org?

Also from that thread:

Moby = open source development

Docker CE = free product release based on Moby

Docker EE = commercial product release based on Docker CE.

Nothing is dead; and everything that was open-source remains open-source. In fact we are open-sourcing new things.

Re: A new upstream project to break up Docker into independent components

#22
post #20

From comment by @stykes on the pull request: Moby = open source development Docker CE = free product release based on Moby Docker EE = commercial product release based on Docker CE. Nothing is dead; and everything that was open-source remains open-source. In fact we are open-sourcing new things.

The pre-emptive defensiveness of that comment says a lot...

Re: A new upstream project to break up Docker into independent components

#23
This is the one of the worst kind of business decision one can make. But I am not theirCTO and CEO. While not the same as Vagrant being replaced (and then revived because the alternate project was a burden), feels the same shitty decision IMO. Plently of people run successful OSS under the same name. Disappointing.

Re: A new upstream project to break up Docker into independent components

#24
post #5

More information can be found there: https://github.com/moby/moby/pull/32691 > Docker is transitioning all of its open source collaborations to the Moby project going forward. Should I understand that the core team wants to keep the brand "Docker" but use it in a commercial way, while Moby will be the underlying open source code? Is it Docker/Moby = RHEL/Fedora ? or Docker/Moby = Mongodb.com/Mongodb.org?

Summoning dang to update link.

Re: A new upstream project to break up Docker into independent components

#28

Excerpts from mobyproject.org give a much better explanation: Moby is an open framework created by Docker to assemble specialized container systems without reinventing the wheel. It provides a “lego set” of dozens of standard components and a framework for assembling them into custom platforms. Audience Moby is recommended for anyone who wants to assemble a container-based system, this includes: Hackers who want to c…

Thank you for ELI5! (The official explanation made no sense to me at all.)

Re: A new upstream project to break up Docker into independent components

#29

I have no idea why they'd want to change such a great name. I am very disappointed. http://www.urbandictionary.com/define.php?term=docker

I'm sure you'll clean up your phrasing (since you're getting downvoted for some reason) but could I ask, is this something you really first thought of when you heard the name? Is it UK slang? I've never heard it. I don't think you should be downvoted for the info (even though it doesn't actually apply, they will keep the name for their commercial stuff) as it's news to me.

Living here, I don't think this use is common in the UK at all.

Re: A new upstream project to break up Docker into independent components

#30
post #20

From comment by @stykes on the pull request: Moby = open source development Docker CE = free product release based on Moby Docker EE = commercial product release based on Docker CE. Nothing is dead; and everything that was open-source remains open-source. In fact we are open-sourcing new things.

The pre-emptive defensiveness of that comment says a lot...

Maybe. The defensiveness could likely be that in many rebrands things tend to get lost in the scuffle (e.g. documentation not fully up to date; difficult to find references to some subproject's new name; checkbox for feature still listed on the enterprise version's landing page; assumption that it was made closed-source). The devs just want to get ahead of that as much as possible.
Post reply on HN