Clangd roadmap? #766
Replies: 3 comments 2 replies
-
I'm happy to start by sharing my own plans and opinions about project needs. Plans Here are some of the things I hope to tackle in the coming months:
Needs
|
Beta Was this translation helpful? Give feedback.
-
Thanks! This was something we've discussed internally a lot but never get to do. Mostly because of maintenance burden and our planning being split between open-source clangd-related stuff and improvements to $Employer's other c++ tooling needs. Main questions that pop into my mind are:
I feel like it might be more feasible to have a markdown file checked in to either clangd/clangd or llvm-project/llvm talking about what people are "actively" working on. Rather than a roadmap, we can have a "Stuff we are working on" section that any contributors can send patches to update and maintainers will approve as usual (the approval here means maintainers are also committing to review changes, participate in design discussions and maintain the result afterwards). As for why:
As for "needs":
This is much riskier and harder to maintain. As the items in this list would need to be prioritized somehow. For example it wouldn't be really desired by maintainers to work on (either drive the change or just provide review/design input) some project that'll impact only a small set of users when there are other items that can benefit a much larger user base. Maybe we can have a list of maintainer approved "needs" (that require multi-week commitment) which can guide new contributors, saying this is by no means a binding list that people should feel forced to, but more of a "patches welcome" list. |
Beta Was this translation helpful? Give feedback.
-
As an example, I think "Google is investing time in 2021 into the development of a protoype for a pseudo-parser with the aim of making some clangd features more responsive" would have been a worthwhile piece of information to communicate to the broader community, using something like a roadmap. (Exciting project btw!) |
Beta Was this translation helpful? Give feedback.
-
Clangd gets contributions from a variety of sources. Some are from volunteers and some from people paid to work on clangd by various organizations.
I think it would be valuable for the community (both contributors and users) to gain some insight into what regular (or even occasional) contributors plan to work on in the upcoming [whatever your planning time-horizon is, likely to vary from person to person]. (Obviously, these would be non-binding outlines of plans, we all know priorities and circumstances change over time.)
In addition, I think it would be valuable to share what are some areas of improvement people think the project needs, even if they're not things you plan to or are able to work on yourself. These could be accumulated into a list (less granular than "all open issues") that could serve as inspiration for contributors looking for something to work on.
Over time, these lists of plans and needs could be massaged into a project roadmap of some sort.
Beta Was this translation helpful? Give feedback.
All reactions