4 ms·
Yes, I can explain. Look at this issue https://github.com/opencontainers/image-spec/issues/24 https://github.com/opencontainers/image-spec/issues/24 and notice
by timthelion 10y ago
Yes, I can explain. Look at this issue https://github.com/opencontainers/image-spec/issues/24 https://github.com/opencontainers/image-spec/issues/24 and notice the belligerant and proprietary attitudes of the Docker employee. He thinks that because the standard is based on the Docker project, he somehow has more say in what will be decided than the other speakers. There is an implied ownership which is not translated when the donation takes place.
- justincormack 10y agoWell I see a CoreOS employee saying that the spec should remain compatible with Docker until after 1.0. The image spec was not "donated" to OCI, various people decided to make a spec for roughly what Docker was doing already, in order to formalise it, with an agreement to do a 1.0 quickly. It was not a standard to create an all new spec, at least initially. There are a lot of existing images out there, so incremental change and backward compatibility is important.