Update 2018-06-18-sip-minutes.md

Author: darjutak

_sips/minutes/2018-06-18-sip-minutes.md

@@ -43,7 +43,7 @@ Minutes were taken by Darja Jovanovic.
 
 Quorum was not met, but the meeting still took place in a form of an open discussion. 
 
-The meeting was devoted to discussing how we would handle the approval of Scala 3 changes into the specification and how we would organize during the next year, given that Scala 3 will be feature freeze by then.
+The meeting was devoted to discussing how SIP Committee should handle the approval of Scala 3 changes into the specification and how it would organize during the next year, given that Scala 3 will be feature freeze by then.
 
 Topics discussed:
 
@@ -61,13 +61,13 @@ Given the short time and amount of decisions that need to be made, the Committee
 
 *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 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
+a) Have a **list of changes**, grouped in batches that would be decided within the next year, meeting once a month
+b) **Plan** - full and strucutured list of changes that need to be implemented consolidated between the Committee members using a shared a Google doc
+c) **Public comments** - each batch should be published on the Contributors thread, for a month at a time in order to have community involved, share their opinion and contribute. Advise was proposed - each thread should clearly point out start and end date of collecting the comments/suggestions.
 
 *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.
+**Jorge** will be in charge of posting the monthly batches on contributors thread. One of the Committee Members (SIP reviewer) or SIP author will be assigned/volunteer to follow the conversations, answer questions and finally summarize the discussion to be submitted to the Committee in order to make inclusive decision.
 The first batch should be the removals as per list already prepared for 2.14 release.
 
 The above mentioned structure and organisation was gathered throughout the meeting, here are the snippets:
@@ -80,9 +80,9 @@ The above mentioned structure and organisation was gathered throughout the meeti
 
 4. Other: spec, quorum
 
-**Heather** bings up a question about Scala spec ([YouTube time: 4'49''](https://youtu.be/q2LVmTe9qmU?t=289)) to which **Martin** responds within the next year we should know which features are included as a first priority but that spec should not be left for the last minute.
+**Heather** bings up an important question "What about Scala spec" ([YouTube time: 4'49''](https://youtu.be/q2LVmTe9qmU?t=289)) to which **Martin** responds within the next year we should know which features are included as a first priority but that spec should not be left for the last minute.
 
-**Miles** ([YouTube time: 8'45](https://youtu.be/q2LVmTe9qmU?t=525)) asks PLEASE ADD
+**Miles** ([YouTube time: 8'45](https://youtu.be/q2LVmTe9qmU?t=525)) states that SIP proposals should be directly linked to specification changes which will save a lot of time and effort.
 
 **Martin** ([YouTube time: 37'59''](https://youtu.be/q2LVmTe9qmU?t=2279)) also raised a question about the decision making process, asking if it would be better to change to simple majority when it comes to voting. This was rejected by most of the Members and agreed it should be discussed in a different meeting or time.