<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Hey folks,</div>
<div><br>
</div>
<div>IRC and mailing list were going far too slow for us to make progress on the competing specifications for handling Dockerfile customization. Instead we held a hangout, which I don't like because it isn't recorded, but it is high bandwidth and permitted
us to work through the problem in 1 hour instead of 1 month.</div>
<div><br>
</div>
<div>The essence of the discussion:</div>
<ol>
<li>I will use inc0's patch as a starting point and will do the following:
<ol>
<li>Prototype base with <block> operations using the specification items in the elemental DSL</li><li>Prototype mariadb with <block> operations using the specification items in the elemental DSL</li><li>I will create a document assuming these two prototypes work that describe how to use the jinja2 <block> operations to replace or merge sections of Dockerfile.j2 files.</li><li>We will stop specification development as it has served its purpose (of defining the requirements) assuming the prototypes meet people's taste test</li></ol>
</li><li>We believe the Jinja2 <block> operation will meet the requirements set forth in the original elemental DSL specification</li><li>We as a community will need to modify our 115 dockerfiles, of which I'd like people to take 1 or 2 container sets each (40 in total), in a distributed fashion to implement the documentation described in section 1.3</li><li>We will produce an optional DSL parser (based upon the prototyping work) that outputs the proper <block> Dockerfile.j2 files or alternatively operators can create their own block syntax files</li><li>All customization will be done in one master block replacement file</li><li>Original dockerfile.j2 files will stay intact with the addition of a bunch of block operations</li><li>Some RUN layer compression will be lost (the && in our Dockerfiles)</li><li>There are 8 DSL operations but we will need twice as many to handle both override and merging in a worst case scenario. That means 16 blocks will need to be added to each Dockerfile.</li><li>Operators that have already customized their Dockerfile.j2 files can carry those changes or migrate to this new customization technique when this feature hits Newton, up to them</li><li>If the prototypes don't work, back to the drawing board – that said I am keen to have any solution that meets the requirements so I will do a thorough job on the prototypes of inc0's work</li></ol>
<div>If you have questions, or I missed key points, please feel fee to ask or speak up.</div>
<div><br>
</div>
<div>Regards</div>
<div>-steve</div>
<div><br>
</div>
</body>
</html>