./menzies/dagstuhlManifesto.md

[timm]

After review, relabel to 'reviewTwo'. After second review, relabel to 'EditorsComment'.

[hongyujohn]

Title of chapter

Perspectives on Data Science for Software Engineering

URL to the chapter

https://github.com/ds4se/chapters/blob/master/menzies/dagstuhlManifesto.md

Message?

This is an introduction to this book.

Accessible?

Yes, the chapter is written in an accessible manner, and is suitable for general audience.

Size?

Yes

Gotta Mantra?

Yes

Best Points

Good desriptions about the motivation of this book.

Things to Change

There are several typos in the chapter. For example: . colloberating => collaborating . this book explore => this book explores . data analytucs => data analytics . we have create => we have created . All this information => All these information

What is "minute to minute actions"?

About the definition of "products", need to make sure that it is consistent across the entire book.

The second reference is not used? [2] F. Akiyama, “An Example of Software System Debugging,” Information Processing, vol. 71, 1971, pp. 353-359.

[miryung]

Title of chapter

Perspectives on Data Science for Software Engineering

URL to the chapter

https://github.com/ds4se/chapters/blob/master/menzies/dagstuhlManifesto.md

Message?

The chapter motivates the book based on a dagstuhl workshop. I was a bit confused with the first sentence, "That workshop documented the range of work on software analytics, with the following premise: So little time, so much data." Is the "so little time" an important piece to motivate the data science for software engineering? The reason why I am asking this question is that, "regardless of analysis time, software archive data seem worth studying for."

Accessible?

The chapter is written for general audience.

Size?

The size is appropriate.

Minor edits: etc => etc. colloberating => collaborating What is "greenfield" in the "greenfield as well as on-going maintenance"? this book explore => this book explores into that process. => into software development process Dagstuhl conference=> Dagstuhl workshop the field on industrial and academic data mining.=> the field on industrial and academic data mining of software (?)

excessive and confusing techno-speak.=> I don't know what "techno-speak" means here.

Gotta Mantra?

I like the title as is.

Best Points

The chapter provides a good overview of the book and why compiling a book on data science in software context is important. If this chapter is to serve the overview of the entire book, I hope it includes a table of content.

[timm]

thanks to @hongyujohn and @miryung. Chapter revised!

for both reviewers:

• [x ] fix typos

for @hongyujohn hongyujohn

• [x ] removing missing reference
• [ x] define "products"

for @miryung

• [x ] fix confusing para1
• [ x] talk to the TOC issue