carette
2018-5-3 12:38:38

Are we going to send suggestions of reviewers?


carette
2018-5-3 12:42:49

What about Rodrigo de Salvo Braz? Bernd Fischer? Avi Pfeffer?


ccshan
2018-5-3 12:50:07

I was thinking Daniel Huang, perhaps Jean-Baptiste Tristan, who else? Klaus Osterman?? Tiark Rompf??


carette
2018-5-3 12:59:14

I would be fine with any of those (additional?) names.


carette
2018-5-3 13:00:12

Though Daniel might be a little too ‘junior’ in a case like this. We need some ‘weight’ on our side.


carette
2018-5-3 13:00:57

Plus, if we suggest a lot of names, I guess that means we have less of a chance of knowing who it eventually is. [And it’s mildly embarassing to the ICFP PC… which I think would be a good thing to do.]


ccshan
2018-5-3 13:02:10

What about adding Guy Steele? Or “PLDI reviewer A”?


carette
2018-5-3 13:03:40

No idea if Guy Steele knows about probabilistic programming - I’ll trust you on that front. “PLDI reviewer A” is an interesting thought indeed!



carette
2018-5-3 13:33:02

Thanks. So we now wait for @samth to chyme in?


samth
2018-5-3 13:34:12

Any of those names are good, although Guy was on my thesis committee


carette
2018-5-3 13:35:03

How long ago was that? Most conflicts rules have time limitations.


carette
2018-5-3 14:05:57

So I did a little sleuthing - seems like that was in 2010. 8 years is long enough ago!


carette
2018-5-3 14:06:27

@ccshan I think this means we can include Guy Steele. And perhaps send the list now, unless @samth wants to include more names?


pravnar
2018-5-3 17:48:47

How about Martin Vechev?


ccshan
2018-5-3 17:49:24

Yeah… Will queue for next email to Tanter.


carette
2018-5-3 18:29:13

So we should still prepare our response, at least to the reviews we do have.


carette
2018-5-3 18:29:43

Due tomorrow and all that.


samth
2018-5-3 18:42:31

Yes. I’ll be around in 40 minutes or so to work on this


ccshan
2018-5-3 19:29:51

I committed some text scraps for the author response, and Sam is typing


carette
2018-5-3 19:41:56

I’ll wait for Sam’s check-in to do more than comment on the text scraps — too high a chance of useless interference.


ccshan
2018-5-3 19:42:44

You can think about what to say and what not to say in the response


carette
2018-5-3 19:43:12

I have indeed thought about that. And am continuing to do so.


carette
2018-5-3 19:44:39

It seems to me that non-experts might not really “get” how hard (and important) arrays were to add to this.


carette
2018-5-3 19:45:41

And FP non-experts might over-value the use of recursion (general or otherwise) in probabilistic modelling.


samth
2018-5-3 19:47:11

Sorry I was not checking in something to that


samth
2018-5-3 19:47:16

so comment now


carette
2018-5-3 19:50:20

Comment or write?


ccshan
2018-5-3 19:52:50

Jacques, you have the edit lock for at least 30 minutes


carette
2018-5-3 19:53:05

Ok, using it now.


rjnw
2018-5-3 20:02:31

isn’t a shared google doc better for doing collaborative editing?


carette
2018-5-3 20:04:12

I’m fine with that. I’ve checked in a first pass of the thoughts I had - if you want to start a Google Doc, now’s a good time.



carette
2018-5-3 20:22:45

Note: the explicit answers to Rev. A are really good!


carette
2018-5-3 20:25:00

Generally, I find that there is very little to say to Rev. B and C (beyond what I wrote online now). Seems B should be told that his ‘call’ that we’re out-of-scope has been overruled. And I don’t think there’s anything we can say to C (or want to) to get a grade change. The paper is too technical to appeal to someone who rates themselves a Z.


carette
2018-5-3 20:31:46

In any case, I’ve written what I can in the Google Doc. There were no questions on either the symbolic parts (where I am quite knowledgeable), or histogram (Ken’s the expert, but I do understand it all).


ccshan
2018-5-4 03:22:44

I drafted a response in the Google Doc.