Cody, I agree it would be nice to have a clear picture of the path to .NET Core, etc. However, at this time, there are very limited resources and too many unknowns to start setting those sorts of expectations. ;-)
You speak of migration of "modules" here, but it is unfortunately not quite that simple. DNN Platform is built on :"ASP.NET Framework". That is a different framework than "ASP.NET Core". The entire foundation of DNN has to be rewritten in order to make a full transition to .NET Core. One step that is being discussed, for example, is to make many APIs .NET Standard compliant (which can run on both "ASP.NET Framework" and "ASP.NET Core" - see https://docs.microsoft.com/en-us/do...t-standard for a nifty little chart on what versions of what work on what versions of what). This effort alone could be 1000s of hours of effort. Now, if we had a team of architect level engineers, this would be less of a mountainous task. However, we don't. We have a handful of people that are contributing to DNN Platform today and only a few people with the actual skill set to accomplish a feat such as this. And, oh by the way, did I mention this is a 100% volunteer effort in an open-source project? Hehe - hopefully, some of these statements are starting to make more sense now.
So, that said, the enthusiasm and passion is absolutely FANTASTIC! We just need to temper our expectations according to the realities of the resources at play here - people, skillset, tools and time. Let's be strategic moving forward. Let's focus on the things we can make better and march forward with a setup for success!