3 ms·

Why would you have to sign a NDA to create an open source ecosystem around an open source project with an Apache 2.0 license?

• 23david 12y ago
  Not sure. Never heard of an official partnership program either, so I'm interested to know details about how this partnership program works. Could be innocent, but something about it smells like a OSS shakedown to me. Just 'cause it's open-source doesn't mean there aren't any politics involved in what gets merged or not. An example: lmctfy support was added by the Google GCE team a long long time ago and I attended a meetup where the GCE team submitted the pull request right there... it was never merged. Languished for months without any public review comments from Docker maintainers. I'd never seen anything like this before. Here we have Google engineers integrating their work with Docker on their own time and being completely ignored. Embarrassing is a nice way to put it. There may have been outside discussions and real issues that made merging a bad idea, but as an OSS project I expect those discussions to happen in the pull request, not in some business meeting. I'm sure any technical issues would have been addressed if there had been any. I'm also sure that the GCE team would have been more than happy to maintain their driver. Politics and open-source are a happy mix. sources: https://github.com/docker/docker/pull/4891 https://github.com/docker/docker/issues/4874
  • nickstinemates 12y ago
    > There may have been outside discussions and real issues that made merging a bad idea Yeah, and Eric Brewer got on stage at DockerCon June and stated that pretty publicly. So your instinct was right.
    • 23david 12y ago
      Part of the problem here could definitely be communication. For whatever reason, it's been incredibly hard to follow what is going on with the Docker project. Keeping info in one place would definitely help. I'm not able to find any details that support what you're saying. It seems that in June Eric Brewer was still publicly asking for libcontainer to merge in LMCTFY support. I definitely could be wrong, but looking at this screenshot from Eric's June talk it looks like they were still trying to get it merged: https://pbs.twimg.com/media/B4DKb51CYAA687s.jpg:large https://pbs.twimg.com/media/B4DKb51CYAA687s.jpg:large In June, Eric Brewer posted this: We’ve released an open-source tool called cAdvisor that enables fine-grain statistics on resource usage for containers. It tracks both instantaneous and historical stats for a wide variety of resources, handles nested containers, and supports both LMCTFY and Docker’s libcontainer. It’s written in Go with the hope that we can move some of these tools into libcontainer directly if people find them useful (as we have). http://googlecloudplatform.blogspot.com/2014/06/an-update-on-container-support-on-google-cloud-platform.html http://googlecloudplatform.blogspot.com/2014/06/an-update-on...
    • Alupis 12y ago
      If this happened, it would be normal and expected for that to be noted on the PR/Issue Ticket. How can you expect someone say 6 months - 1 year from now to know this unless it's clearly documented? That is what the Issues system is for.