<font size=2 face="sans-serif">As promised, I've moved the code over from
carlbrown/HTTPSketch to swift-server/http into a "develop" branch:</font>
<br><font size=2 face="sans-serif"> </font><a href="https://github.com/swift-server/http/tree/develop"><font size=2 color=blue face="sans-serif">https://github.com/swift-server/http/tree/develop</font></a>
<br>
<br><font size=2 face="sans-serif">There's been three minor changes:</font>
<ol>
<li value=1><font size=2 face="sans-serif">I've updated the licence to
match the Swift.org licence and added copyright headers</font>
<li value=2><font size=2 face="sans-serif">I've added a API.md file to
describe what the current API in the branch is</font>
<li value=3><font size=2 face="sans-serif">Carl has moved SimpleResponseCreator
into Tests</font>
<li value=4></ol><font size=2 face="sans-serif">The next step is to go through
a staged review. As its WWDC/AltConf/etc next week a number of people will
be busy, as such it doesn't make sense to have a strict schedule until
after next week. Having said that, we should try to make progress and close
down/agree on some of the types if we can. </font>
<br>
<br><font size=2 face="sans-serif"><b>Paulo:</b> As
an relatively small starting point, do you want to raise a PR to discuss
making HTTPVersion a struct?</font>
<br>
<br><font size=2 face="sans-serif">If can close that down it might make
sense to then move onto HTTPMethod and HTTPResponseStatus/HTTPStatus as
those are again relatively small and we might be able to close them out
during the busy week.</font>
<br>
<br><font size=2 face="sans-serif">Chris<br>
</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Chris Bailey via swift-server-dev
<swift-server-dev@swift.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif"><swift-server-dev@swift.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">30/05/2017 19:13</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">[swift-server-dev]
HTTP API: prototype review process</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">swift-server-dev-bounces@swift.org</font>
<br>
<hr noshade>
<br>
<br>
<br><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><font size=3>
</font>
<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><font size=3> </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><font size=3>
</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><font size=3>
</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><font size=2 face="sans-serif"><br>
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><font size=3><br>
</font><font size=2 face="sans-serif"><br>
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</font><tt><font size=2>_______________________________________________<br>
swift-server-dev mailing list<br>
swift-server-dev@swift.org<br>
</font></tt><a href="https://lists.swift.org/mailman/listinfo/swift-server-dev"><tt><font size=2>https://lists.swift.org/mailman/listinfo/swift-server-dev</font></tt></a><tt><font size=2><br>
</font></tt>
<br>
<br><font size=2 face="sans-serif"><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>