[research] Provide a report about the studied papers/books around the developer observability topic

[warenlg]

As regards Eng. Observability using ML, the following points have been identified as potential future work directions:

• Gemini: see how much depends on each particular language, re-evaluate weights for UASTv2
• Repository, developer grouping, clustering by several criteria
  • Coding style
  • Languages: ratio, amount
  • Topics
  • Imports
• Developer profiling
• Burndown (project, file, author)
• Ownership: by last changed, by overall efforts, time decay of both
• Core developers analysis (bus factor)
• Overwrites matrix
• Hot spot analysis - IT modernization
• Ranking code by importance
• Commit classifier
• Couples (code units, files, people)
• Aligned commit series: developers, projects

This stands for a lot very different topics, so the task would be to find and study in the literature what has already been tried/done successfully or not towards those topics with a particular focus on the features employed and the evaluation strategy.

Let's collaborate here https://docs.google.com/document/d/1PSl2oIDKKiodsgUduhhX8Uiz6AqTI_UxSS_1w_0KKt4/edit?usp=sharing

[r0mainK]

So along with the google doc that will be separated by topics listed above, we created a folder on the drive for any books/papers that might be of use (link below). I already added the PDF of "Software Design X-rays", if you use anything else it might be easier to just upload it there as well so we don't have to look for it in Slack

[vmarkovtsev]

Done