Thanks. I suppose I probably should have started with a different question:
Do you know what parts of Ubuntu Touch were abandoned by Canonical when development of Ubuntu Touch stopped? Did they only stop the packaging aspect of the project? Or did they also stop development of other core pieces of technology (e.g. Unity, Mir, Wayland, middleware layers, etc)? I suspect that since the newest Ubuntu release no longer features Unity, that development on Unity might have been stopped as well (or at least the Convergence feature of it), but this is purely a guess. Does anybody know for sure?
If all they did was stop the packaging aspect, well, that might change my answer to your questions a bit... I suppose I was starting from the assumption that some of the software that's needed to make Ubuntu Touch work was likely abandoned when Ubuntu Touch was. That could have been incorrect.
Anyways, to answer your questions, if any of the UI parts were abandoned (Unity, mobile UI features, etc) then I'd probably be most interested in working on that. Though I also wouldn't mind getting involved with middleware or backend stuff either. I've heard rumors that the Ubuntu Touch emulator no longer works, if that's still the case, I think that would also be interesting to try and fix.
I have 13 years of experience with C, C++, Python, Qt, and Gtk, but no real experience yet with kernel/driver programming.
Anyways, perhaps someone can provide some insight as to what the needs are on the project, what software (if any) was abandoned by Canonical when Ubuntu Touch was, etc. I'd certainly be interested to hear the scoop.
Thanks!