Hi, thanks for sharing your proposal here. My first reaction is that you’re planning to take on too much here. This stuff will almost always take longer than you think. This matters even more when GSoC is only part time this year.
However, my larger concern is that some of these changes conflict with work I’m doing on curves currently. Currently there is some design / planning for adding curve support to geometry nodes. You can find the design here: https://wiki.blender.org/wiki/Modules/Physics_Nodes/Projects/EverythingNodes/CurveNodes
Then, everyone basically agrees that the current curve code is messy, and in need of a refactor. So I took this as an opportunity to improve the code with a new implementation. You can find a task to track the work here: T87245: Geometry Nodes: Curve Support Implementation. I’m using C++ here with some more modern / efficient architecture that should be much better in the end.
I don’t speak for everyone here, and I’m obviously biased since I’m the one working on this refactoring, but I would personally much rather see most of these changes like this be done in the context of the above task, rather as iterative changes on the existing code.
This idea was added to the list when the plans were less solid, so sorry for the confusion. However, I think there is still room for a project here. By the summer these changes might be a lot further along, so one option is to work with the new curve code. Though it’s not absolutely certain what the status of the branch will be. Another option is to find the space of least overlap with the plans above and work there. That is likely the curve edit mode changes you propose, though I still have some of the same reservations about that.