[proposal] Migrating ndt_omp into Autoware Universe

[kminoda]

I propose to migrate ndt_omp package, which is currently treated as an external package,into Autoware Universe as a new package.

Reason:
I am currently working on dynamic map loading (DML) (please see this discussion for details). The implementation would include a large modification in ndt_omp package, which is originated from https://github.com/koide3/ndt_omp.

Originally, the package was maintained as a vendor package in Autoware until now so that we can sync with the upstream at a low cost. However, after the above modification on ndt_omp, it would be difficult to sync with the upstream, and would also be highly dependent on Autoware Universe. Thus, I think it would be better to migrate the package into Universe for easier implementation at this point.

Let us know if you have any opinions on this. I would wait for a week (let me know if this is too short!), and unless I see any disagreement, I would port the package into Universe.

FYI: This is the migrating PR

[kenji-miyake]

The implementation would include a large modification in ndt_omp package
would also be highly dependent on Autoware Universe

@kminoda Could you explain these changes more concretely? Without that information, we can't judge whether it's appropriate to manage the package in autoware.universe.
I feel it's weird that ndt_omp, which is a library, depends on autoware.universe, which is a set of applications.

[kminoda]

Thank you for the opinion! After re-thinking internally, we've decided not to do the migration for now.