Skip to content

Commit 364ff75

Browse files
authored
Merge pull request #2 from scala/sip-summary-updates
SIP meeting summary - updating filename, additions
2 parents a328e2b + 083b73b commit 364ff75

File tree

1 file changed

+22
-19
lines changed

1 file changed

+22
-19
lines changed

blog/_posts/2016-07-15-sip-summary-minutes.md renamed to blog/_posts/2016-07-20-sip-summary-minutes.md

Lines changed: 22 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -2,53 +2,56 @@
22
layout: blog
33
post-type: blog
44
by: Jorge Vicente Cantero
5-
title: SIP Meeting Results: 2 SIPs Numbered and 3 SIPs Updated
5+
title: "SIP Meeting Results: 2 SIPs Numbered and 3 SIPs Updated"
66
---
77

8-
Yesterday the Scala Center ran its first SIP meeting under the [newly reformed SIP
8+
Last week, the Scala Center ran its first SIP meeting under the [newly reformed SIP
99
process](http://docs.scala-lang.org/sips/sip-submission.html), and we're happy
1010
to report that several SIPs saw long-awaited decisions made, or received
1111
detailed feedback from the SIP committee!
12-
12+
1313
In the new SIP process, each SIP is assigned a reviewer, who must be someone
1414
sitting on the SIP committee. The reviewer's job is to carefully read and
1515
understand the SIP, and to present the SIP before the SIP committee. The
1616
reviewer must also present their analysis of the SIP to the committee, and then
1717
the floor is opened up for discussion on the SIP. An explicit goal of the new
1818
SIP process is for a decision and next steps to be determined for each SIP
19-
discussed.
20-
19+
discussed.
20+
2121
The SIP committee went through five SIPs in the queue. Two new SIPs received a
2222
number, meaning they passed the first phase of acceptance – that is, the change
2323
to Scala is accepted in theory, so long as the the committee's design and
2424
implementation concerns can be adequately addressed in subsequent discussions on
2525
the SIP. The two SIPs which received numbers (first-round accepted) include:
26-
* [SIP-26 Unsigned Integer Data Types](https://github.com/scala/slip/pull/30)
27-
* [SIP-27 Trailing Commas](https://github.com/scala/scala.github.com/pull/533)
28-
26+
27+
* **[SIP-26 Unsigned Integer Data Types](https://github.com/scala/slip/pull/30)**, Reviewer: Martin Odersky ([review comments](https://github.com/scala/slip/pull/30#issuecomment-232399052))
28+
* **[SIP-27 Trailing Commas](https://github.com/scala/scala.github.com/pull/533)**, Reviewer: Eugene Burmako ([review comments](https://github.com/scala/scala.github.com/pull/533#issuecomment-232959066))
29+
2930
Two other passed their first iteration as proposed by [the new
3031
process](http://docs.scala-lang.org/sips/sip-submission.html):
31-
* [SIP-25 Trait Parameters](http://docs.scala-lang.org/sips/pending/trait-parameters.html)
32-
* [SIP-20 Improved Lazy Val Initialization](http://docs.scala-lang.org/sips/pending/improved-lazy-val-initialization.html)
33-
32+
33+
* **[SIP-25 Trait Parameters](http://docs.scala-lang.org/sips/pending/trait-parameters.html)**, Reviewer: Adriaan Moors ([review comments](https://github.com/scala/scala.github.com/pull/428#issuecomment-233401911))
34+
* **[SIP-20 Improved Lazy Val Initialization](http://docs.scala-lang.org/sips/pending/improved-lazy-val-initialization.html)**, Reviewer: Sébastien Doeraene ([review comments](https://github.com/scala/scala.github.com/pull/206#issuecomment-232939781))
35+
3436
The final SIP discussed one was postponed at the request of the authors:
35-
* [SIP-22 Async](http://docs.scala-lang.org/sips/pending/async.html)
36-
37+
38+
* **[SIP-22 Async](http://docs.scala-lang.org/sips/pending/async.html)**, Reviewer: Eugene Burmako
39+
3740
In the case of SIP-22, the authors will reopen it when they feel like taking up
3841
the proposal again, and addressing the issues they must look into next; in
3942
particular, figuring out how async/await can be used inside of a try/catch
40-
block.
41-
43+
block.
44+
4245
Overall, we're happy to report that progress was made on a number of SIPs in the
4346
queue. In particular, we're excited that 2 SIPs received a first-phase of
4447
acceptance in receiving their numbers, and look forward to the addition of these
45-
proposals to Scala soon!
46-
48+
proposals to Scala soon!
49+
4750
Next month, we will propose a reformed SLIP process focused on shaping this new
4851
notion of the Scala "platform," with a completely new committee, consisting of
4952
Scala community members. Keep an eye out for developments on the Scala library
50-
front this August!
51-
53+
front this August!
54+
5255
Did you know that each month, we conduct our SIP meetings on-air? You can tune
5356
in and ask questions to the SIP committee, and have them answered live! You can
5457
even watch [past SIP meetings](https://plus.google.com/+ScalaProcess) at any

0 commit comments

Comments
 (0)