Re: KDevelop problems suitable for a Ph.D. thesis

Hi!

Thanks to everyone who replied. The past KDevelop studies will help me define 
and substantiate scientific significance of my work.

I am lucky to have a professor who is happy with the theme of my choice. 
Motivation, existing skills and practical results are also very important. The 
agreed upon theme is "Optimizing an IDE", where "optimizing" means any 
interesting improvements, not necessarily performance, that I come up with. 
Turns out that inventing a new algorithm is not a hard requirement and 
"innovative" processes/workflows, etc. can also be part of a thesis. Though of 
course a new algorithm would be nice to have. Hopefully I'll find suitable 
problems while working on the thesis in the next few years.

As for the specific problems proposed so far:
1. The LSP protocol integration is back on the table because of the practical 
significance of supporting many new languages.
2. The Zealdoc plugin doesn't seem to be a cool feature or particularly 
interesting to implement. But I'll check it out, maybe I'm mistaken.
3. My professor appreciates the usefulness of solving the code meta information 
problem. Whether I work on it will depend on how interesting and feasible the 
required duchain changes are.
4. I am not a fan of AI code assistants myself and wouldn't want the IDE to 
occasionally unexpectedly provide not always useful suggestions. Another concern 
is the temptation to deliberately (mis)name an identifier in a way that triggers 
an AI hint. So my personal motivation for this feature is low.

Now I am going to prepare to exams to win the postgraduate competition. 
Therefore, I will not be actively contributing to KDevelop in the next week or two.

Thanks again,
Igor