<font size=2 face="sans-serif">I've had some discussions with Paulo and
David Ask offline, and below is the proposal from Paulo on how we proceed:</font>
<br>
<ol>
<li value=1><font size=2 face="sans-serif">Move the HTTP Sketch prototype
(of Johannes' API proposal) into the swift-server repo<br>
This will go into a “develop” branch rather than "master",
but will have a MVP semver tag so it can be included via SwiftPM for people
to test and benchmark with.</font>
<li value=2><font size=2 face="sans-serif">Have a staged review of the
types and APIs<br>
In order to make sure that we have full "review coverage", we'll
structure reviewing and reaching agreement on the types and APIs, including
having deadlines for discussion, updates and reaching a conclusion.</font>
<li value=3><font size=2 face="sans-serif">Reviewed types and APIs are
then merged into master<br>
Once a set of types or APIs have been reviewed, AND they build, pass tests
with at least (95%?) coverage, 100% doc coverage, have generated jazzy
docs and as well as design docs including the rationale for design decisions.</font>
<li value=4><font size=2 face="sans-serif">When the full set of types and
APIs have been reviewed and merged to master, raise a Swift Evolution Proposal<br>
Once there is a full implementation in master, the API spec will go forward
as a Swift Evolution Proposal to get feedback from the wider community.
Once the feedback from the community is included, we can look at tagging
a 1.0.0 release based on master.</font></ol>
<br><font size=2 face="sans-serif">We'll also document the API separately
etc as suggested by Helge Heß. If this seems like a reasonable approach,
we'll move the prototype code over to the swift-server org into a "develop"
branch tomorrow. </font>
<br>
<br><font size=2 face="sans-serif">Chris<br>
Unless stated otherwise above:<br>
IBM United Kingdom Limited - Registered in England and Wales with number
741598. <br>
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU<br>
</font>