Update 2018-5-18.md

Author: darjutak

_sips/minutes/2018-5-18.md

@@ -25,11 +25,14 @@ Minutes were taken by Darja Jovanovic.
 * Heather Miller ([@heathermiller](https://github.com/heathermiller)), Scala Center
 * Sébastien Doeraene ([@sjrd](https://github.com/sjrd)), EPFL
 * Adriaan Moors ([@adriaanm](https://github.com/adriaanm)), Lightbend
-* Miles Sabin ([@milessabin](https://github.com/milessabin))
-* Darja Jovanovic ([@darjutak](https://github.com/darjutak)
+* Miles Sabin ([@milessabin](https://github.com/milessabin)), Independent
+* Darja Jovanovic ([@darjutak](https://github.com/darjutak)), Scala Center
 
 ## Not present
 
+* Iulian Dragos ([@dragos](https://github.com/dragos)), Triplequote
+* Eugene Burmako ([@xeno-by](https://github.com/xeno-by)), Twitter
+* Josh Suereth ([@jsuereth](https://github.com/jsuereth)), Independent
 
 
 ## Proceedings
@@ -47,18 +50,20 @@ All present agreed that SIP Committee should continue its mandate in approving t
 
 2. SIP Committee role in Scala 2
 
-SIP Committee will focus on Scala 3 changes and creating the spec, **Martin** [YouTube time: 6'54''](https://youtu.be/q2LVmTe9qmU?t=414), Scala 2 SIP proposals will continue as before, but in a slower paste.
+SIP Committee will focus on Scala 3 changes and creating the spec, **Martin** [YouTube time: 6'54''](https://youtu.be/q2LVmTe9qmU?t=414), Scala 2 SIP proposals will continue as before, but at a slower pace.
 
 3. How to structure and organise the workflow
 
 Given the short time and amount of decisions that need to be made, the Committee proposed and agreed about the following
 
 *Structure*
+
 a) Have a **list of changes**, separated in batches that would be decided within the next year, meeting once a month
-b) **Plan** should be consolidated between the Committee members through a Google doc
+b) **Plan** should be consolidated between the Committee members using a shared a Google doc
 c) **Public comments** - each batch should be published for a month before discussing on the Contributors thread in order to have community involved, share their opinion and contribute in the proposed changes. The discussions should be in a month time frame, and clearly stated at the beginning of the thread
 
 *Organisation*
+
 **Jorge** will be in charge of posting the monthly batches on contributors thread and, depending on the subject, one of the Committee Members or a contributor will follow the conversations, answer questions and finally summarize the discussion to be submitted to the Committee in order to make inclusive decisions.
 The first batch should be the removals as per list already prepared for 2.14 release.