Speaking for the DevOps, a large part of the job is being responsible for building trusted systems from trusted components. I want to continue considering Docker to be part of that trusted stack, but from looking at the minutes, it seems that you are willing to mislead even large partners like Google while on the record.

  JB (Google): Docker is an anchor of a large ecosystem of projects. Docker Inc 
  bought Fig, is it a separate project or is it going to be in Docker?
  SH: it should be explicit. The Fig guys make proposals and those are reviewed
  as every body else's.
  JB (Google): The idea is we will be more comfortable if we know how to 
  contribute both to Docker and the larger ecosystem. 
  SH: The day after Docker Inc. acquired Fig nothing changed at all, everything
  is still in the Open. The reason for the acquisition was to make Docker more
  user friendly. The experience should be awesome. The more people we can throw
  at the problem the better.
  VL: Understanding what is off limits or at least where the limits are would
  be helpful. This is entirely driven by technology? We can collaborate "here" 
  but maybe we can compete "there".
  BG: It's absolutely right, there is a large number of projects competing with
  Docker Inc. and that's fine. Some folks want Docker to remain a packaging
  format. We should add a statement there on clarifying this.

Source (both as github gist and google doc):

  https://gist.github.com/inthecloud247/00eb3130f728b635db9e
  https://docs.google.com/document/d/1JfWNzfwptsMgSx82QyWH_Aj0DRKyZKxYQ1aursxNorg

Just today, the "Host management" proposal initiated by a Fig developer was closed (by him) without any discussion after he released the new Docker Machine project (which AFAIK was initiated without any public discussion or warning.) https://github.com/docker/docker/issues/8681