Minutes for May 2017, draft 0 #868

darjutak · 2017-08-17T09:01:50Z

No description provided.

copied from november 2016

The file was a test, no need to keep it anymore (o:

This version needs to be reviewed

…cala-lang into darjutak-patch-1

darjutak · 2017-08-17T09:05:48Z

_sips/minutes/2017-05-08-sip-minutes.md

+| --- | --- | --- |
+| [SIP-NN - comonadic-comprehensions](http://docs.scala-lang.org/sips/comonadic-comprehensions.html) | Shimi Bandiel | Rejected |
+| [SIP-33 - Match infix & prefix types to meet expression rules](http://docs.scala-lang.org/sips/make-types-behave-like-expressions.html)| Oron Port | Pending |
+|Scala Library Changes|Adriaan Moors| **WHAT DO I PUT HERE** |


Please check the third item, it doesn't seem to be a SIP, what do we put it in the columns?

@jvican could you chime in here? (I wasn't present for the meeting)

I would put "Scala-dev proposal" and link to scala/scala-dev#323.

heathermiller

@jvican can you also review this? It's almost good to go. But there are a handful of misunderstandings in here that you may be able to quickly correct.

heathermiller · 2017-09-08T23:07:09Z

_sips/minutes/2017-05-08-sip-minutes.md

+| --- | --- | --- |
+| [SIP-NN - comonadic-comprehensions](http://docs.scala-lang.org/sips/comonadic-comprehensions.html) | Shimi Bandiel | Rejected |
+| [SIP-33 - Match infix & prefix types to meet expression rules](http://docs.scala-lang.org/sips/make-types-behave-like-expressions.html)| Oron Port | Pending |
+|Scala Library Changes|Adriaan Moors| **WHAT DO I PUT HERE** |


@jvican could you chime in here? (I wasn't present for the meeting)

heathermiller · 2017-09-08T23:11:41Z

_sips/minutes/2017-05-08-sip-minutes.md

+
+**Jorge** is getting back discussion on voting on this proposal and he mentioned that Josh insisted on more examples and suggestions on motivation of this SIP.
+
+**Eugene** wanted to add more syntax (map and flatmap), but Martin opposed to that saying that Scala is quite serious program and needs more reason to add any additional syntax to it. **Martin** would like to see more widespread use of common attic constructs and Libraries, and before doing that, he wouldn’t consider any further change. **Sebastian** agrees with Martin and says that he doesn’t really understand Josh’s and Eugene’s proposal. **Iulian** agrees that the proposal is quite complicated and he wonders how it can be useful. He believes that it is an interesting research direction, but that it needs more users feedbacks in aim to be included in the Scala, therefore questioning if the proposal should be numbered in the current form. Seth and Adriaan agree with Martin and Iulian.


"common attic constructs" seems incorrect. Must be misheard... (Not sure what it's supposed to be)

Can someone go back and listen to the recording to figure out what was said here? This needs to be resolved before this is merged.

perhaps "common attic" is "comonadic"

Common Attic is frequently used words with roots from ancient Greek. Like monad.

heathermiller · 2017-09-08T23:12:15Z

_sips/minutes/2017-05-08-sip-minutes.md

+
+**Eugene** wanted to add more syntax (map and flatmap), but Martin opposed to that saying that Scala is quite serious program and needs more reason to add any additional syntax to it. **Martin** would like to see more widespread use of common attic constructs and Libraries, and before doing that, he wouldn’t consider any further change. **Sebastian** agrees with Martin and says that he doesn’t really understand Josh’s and Eugene’s proposal. **Iulian** agrees that the proposal is quite complicated and he wonders how it can be useful. He believes that it is an interesting research direction, but that it needs more users feedbacks in aim to be included in the Scala, therefore questioning if the proposal should be numbered in the current form. Seth and Adriaan agree with Martin and Iulian.
+
+**Conclusion** Proposal discarded unanimously. They will send the feedback to the author.


Who was supposed to send feedback? Was feedback indeed sent?

Same here. Can someone please have a look to see if feedback was indeed sent?

heathermiller · 2017-09-08T23:13:02Z

_sips/minutes/2017-05-08-sip-minutes.md

+ [YouTube time 10:52](https://youtu.be/6rKa4OV7GfM?t=652)
+
+ **Adriaan** starts presentation and notes that feedbacks on his proposal are available through the 2.13 platform. It is more reorganization of things in different modules. He suggests list of packages, from the ticket, that he believes shouldn’t be in the core:
+ *Scala concurrent*, *Scala.ref*, *Scala.cis*, *Scala.compat* (that is already totally deprecated), *Scala.text* (that has already couple of things that are deprecated), *Scala.util*; whereas *Scala.io* and *Scala.sys* are good candidates for replacements with better community modules.


scala.cis? @jvican do you know which one he was referring to?

Yeah, scala.sys 👍

heathermiller · 2017-09-08T23:13:32Z

_sips/minutes/2017-05-08-sip-minutes.md

+
+ **Adriaan** starts presentation and notes that feedbacks on his proposal are available through the 2.13 platform. It is more reorganization of things in different modules. He suggests list of packages, from the ticket, that he believes shouldn’t be in the core:
+ *Scala concurrent*, *Scala.ref*, *Scala.cis*, *Scala.compat* (that is already totally deprecated), *Scala.text* (that has already couple of things that are deprecated), *Scala.util*; whereas *Scala.io* and *Scala.sys* are good candidates for replacements with better community modules.
+ Also, some hashing could be removed in separate package and make Scala package cut clean. He is open to discuss if some of these packages should stay in the Scala Library Jar. Most of these packages are subjects of deprecations.


"Jar" -> "jar"

heathermiller · 2017-09-08T23:13:54Z

_sips/minutes/2017-05-08-sip-minutes.md

+ **Adriaan** starts presentation and notes that feedbacks on his proposal are available through the 2.13 platform. It is more reorganization of things in different modules. He suggests list of packages, from the ticket, that he believes shouldn’t be in the core:
+ *Scala concurrent*, *Scala.ref*, *Scala.cis*, *Scala.compat* (that is already totally deprecated), *Scala.text* (that has already couple of things that are deprecated), *Scala.util*; whereas *Scala.io* and *Scala.sys* are good candidates for replacements with better community modules.
+ Also, some hashing could be removed in separate package and make Scala package cut clean. He is open to discuss if some of these packages should stay in the Scala Library Jar. Most of these packages are subjects of deprecations.
+ Scala concurrent could live in its current form, but it could be split out since it’s dependent platform however.


"since it's dependent platform"? Not sure what this means.

Maybe "platform dependent" is better?

heathermiller · 2017-09-08T23:14:09Z

_sips/minutes/2017-05-08-sip-minutes.md

+ Also, some hashing could be removed in separate package and make Scala package cut clean. He is open to discuss if some of these packages should stay in the Scala Library Jar. Most of these packages are subjects of deprecations.
+ Scala concurrent could live in its current form, but it could be split out since it’s dependent platform however.
+
+ **Jorge** asks what they should change in XML. **Adriaan** says that it’s already a model and all these packages should wing as Scala changes. If no one from the community does push forward to maintain that, they should continue maintaining them through depreciation cycle, helped by replacement through SPPs. All these packages and classes of packages should be available in 2.13 as Jars, but you should add them by yourself to your classpath if you are using them.


"should wing"? Not sure what this means.

"Jar" should be lowercase

heathermiller · 2017-09-08T23:16:16Z

_sips/minutes/2017-05-08-sip-minutes.md

+
+ **Jorge** proposes to keep thinking on this and to discuss it in the next two months, migration cycle.  
+
+ **Seth** said that 2.13 circle progresses will bring more information and feedback about the usage. He believes that it is a good start to begin with and they’ll know more as they go through it.


"circle progress" not sure what this means.

"said that as the 2.13 cycle progresses"

jvican

@heathermiller Just went through it. It looks solid, but needs the changes that you've already pointed out. I was able to quickly correct some sentences. I'll LGTM as soon as they are addressed 😄.

darjutak · 2017-10-03T08:55:40Z

All changes made as advised (o:
good to merge

SethTisue · 2017-10-15T22:46:00Z

should we merge this now?

heathermiller · 2017-10-16T08:29:13Z

Yes! Thank you @SethTisue and @darjutak!

darjutak added 6 commits August 16, 2017 11:45

Trying the new minutes april 2017

a2ee1a8

copied from november 2016

Changed the title

79a915c

Delete 2017-05-08-sip-minutes.md

2784d99

The file was a test, no need to keep it anymore (o:

2017_05_08_Minutes

7dcbb9a

This version needs to be reviewed

May minutes draft 0

e56c394

Merge branch 'darjutak-patch-1' of https://github.com/darjutak/docs.s…

4127fd7

…cala-lang into darjutak-patch-1

darjutak commented Aug 17, 2017

View reviewed changes

SIP-NN comondic-comprehensions marked as rejected

b726ea1

heathermiller reviewed Sep 8, 2017

View reviewed changes

jvican reviewed Sep 9, 2017

View reviewed changes

Update 2017-05-08-sip-minutes.md

de4bffd

Update 2017-05-08-sip-minutes.md

59babc7

heathermiller merged commit 81d11fe into scala:master Oct 16, 2017


		Jorge is getting back discussion on voting on this proposal and he mentioned that Josh insisted on more examples and suggestions on motivation of this SIP.

		Eugene wanted to add more syntax (map and flatmap), but Martin opposed to that saying that Scala is quite serious program and needs more reason to add any additional syntax to it. Martin would like to see more widespread use of common attic constructs and Libraries, and before doing that, he wouldn’t consider any further change. Sebastian agrees with Martin and says that he doesn’t really understand Josh’s and Eugene’s proposal. Iulian agrees that the proposal is quite complicated and he wonders how it can be useful. He believes that it is an interesting research direction, but that it needs more users feedbacks in aim to be included in the Scala, therefore questioning if the proposal should be numbered in the current form. Seth and Adriaan agree with Martin and Iulian.


		Eugene wanted to add more syntax (map and flatmap), but Martin opposed to that saying that Scala is quite serious program and needs more reason to add any additional syntax to it. Martin would like to see more widespread use of common attic constructs and Libraries, and before doing that, he wouldn’t consider any further change. Sebastian agrees with Martin and says that he doesn’t really understand Josh’s and Eugene’s proposal. Iulian agrees that the proposal is quite complicated and he wonders how it can be useful. He believes that it is an interesting research direction, but that it needs more users feedbacks in aim to be included in the Scala, therefore questioning if the proposal should be numbered in the current form. Seth and Adriaan agree with Martin and Iulian.

		Conclusion Proposal discarded unanimously. They will send the feedback to the author.


		Jorge proposes to keep thinking on this and to discuss it in the next two months, migration cycle.

		Seth said that 2.13 circle progresses will bring more information and feedback about the usage. He believes that it is a good start to begin with and they’ll know more as they go through it.

Minutes for May 2017, draft 0 #868

Minutes for May 2017, draft 0 #868

Uh oh!

Conversation

darjutak commented Aug 17, 2017

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

heathermiller left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

jvican left a comment

Choose a reason for hiding this comment

Uh oh!

darjutak commented Oct 3, 2017

Uh oh!

SethTisue commented Oct 15, 2017

Uh oh!

heathermiller commented Oct 16, 2017

Uh oh!

Uh oh!