|
2 | 2 | layout: blog |
3 | 3 | post-type: blog |
4 | 4 | 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" |
6 | 6 | --- |
7 | 7 |
|
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 |
9 | 9 | process](http://docs.scala-lang.org/sips/sip-submission.html), and we're happy |
10 | 10 | to report that several SIPs saw long-awaited decisions made, or received |
11 | 11 | detailed feedback from the SIP committee! |
12 | | - |
| 12 | + |
13 | 13 | In the new SIP process, each SIP is assigned a reviewer, who must be someone |
14 | 14 | sitting on the SIP committee. The reviewer's job is to carefully read and |
15 | 15 | understand the SIP, and to present the SIP before the SIP committee. The |
16 | 16 | reviewer must also present their analysis of the SIP to the committee, and then |
17 | 17 | the floor is opened up for discussion on the SIP. An explicit goal of the new |
18 | 18 | SIP process is for a decision and next steps to be determined for each SIP |
19 | | -discussed. |
20 | | - |
| 19 | +discussed. |
| 20 | + |
21 | 21 | The SIP committee went through five SIPs in the queue. Two new SIPs received a |
22 | 22 | number, meaning they passed the first phase of acceptance – that is, the change |
23 | 23 | to Scala is accepted in theory, so long as the the committee's design and |
24 | 24 | implementation concerns can be adequately addressed in subsequent discussions on |
25 | 25 | 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 | + |
29 | 30 | Two other passed their first iteration as proposed by [the new |
30 | 31 | 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 | + |
34 | 36 | 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 | + |
37 | 40 | In the case of SIP-22, the authors will reopen it when they feel like taking up |
38 | 41 | the proposal again, and addressing the issues they must look into next; in |
39 | 42 | particular, figuring out how async/await can be used inside of a try/catch |
40 | | -block. |
41 | | - |
| 43 | +block. |
| 44 | + |
42 | 45 | Overall, we're happy to report that progress was made on a number of SIPs in the |
43 | 46 | queue. In particular, we're excited that 2 SIPs received a first-phase of |
44 | 47 | 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 | + |
47 | 50 | Next month, we will propose a reformed SLIP process focused on shaping this new |
48 | 51 | notion of the Scala "platform," with a completely new committee, consisting of |
49 | 52 | Scala community members. Keep an eye out for developments on the Scala library |
50 | | -front this August! |
51 | | - |
| 53 | +front this August! |
| 54 | + |
52 | 55 | Did you know that each month, we conduct our SIP meetings on-air? You can tune |
53 | 56 | in and ask questions to the SIP committee, and have them answered live! You can |
54 | 57 | even watch [past SIP meetings](https://plus.google.com/+ScalaProcess) at any |
|
0 commit comments