This seems like a top priority in a way. But it is hard for me to have a go to place to
see current up-to-date progress made ( so we can feel like we are going somewhere... a moral thing )
things to do (Links to relevant information related to each step to plan forward)
next steps needed to move forward
I feel like this should be on our community site page. A dedicated section for this migration project that is transparent so others can quickly get up to speed and involved with the project if desired.
It is the only way we can push this forward faster IMO. I cannot wait years for current Blazor in .NET Core and Web API features. We need a real aggressive game plan here. Or build a second CMS and leave the others behind entirely.
If mod developers and theme developers dont want to help they might as well be left behind. We are all part of the DNN ecosystem everyone should be helping here in some way.
I almost feel like forking this project and starting a new CMS. I do however like the idea of keeping my modules as is. On the other hand if this is a decade out project... this is no good to me lets start a second project and combine them later when time is right with a way to migrate from one to the other once module developers that are still active create the new version that allows them to migrate what they need.
What can be done in respect to speeding up this project? I am currently trying to dig into things as well I know we are community developers but if we had .NET Core version we would have 1000 contributors.... and growing instead of the other way.
Over the next couple weeks I will read all the code and resources for development of hopefully a few PR's that relate.
Instead of qubits I will be researching with my time migrations from .NET Framework to .NET Core just to help this effort out here.
Any current thoughts here I know I sound like a broken record I just really need to see DNN version .NET Core as I like the CMS features. I can probably recreate all the modules I have and import the data I need. But I don't want to get off topic. I want to get more focused on this effort so I get a good idea of what will get accepted for a PR.
This seems like a top priority in a way. But it is hard for me to have a go to place to
I feel like this should be on our community site page. A dedicated section for this migration project that is transparent so others can quickly get up to speed and involved with the project if desired.
It is the only way we can push this forward faster IMO. I cannot wait years for current Blazor in .NET Core and Web API features. We need a real aggressive game plan here. Or build a second CMS and leave the others behind entirely.
If mod developers and theme developers dont want to help they might as well be left behind. We are all part of the DNN ecosystem everyone should be helping here in some way.
I almost feel like forking this project and starting a new CMS. I do however like the idea of keeping my modules as is. On the other hand if this is a decade out project... this is no good to me lets start a second project and combine them later when time is right with a way to migrate from one to the other once module developers that are still active create the new version that allows them to migrate what they need.
What can be done in respect to speeding up this project? I am currently trying to dig into things as well I know we are community developers but if we had .NET Core version we would have 1000 contributors.... and growing instead of the other way.
Over the next couple weeks I will read all the code and resources for development of hopefully a few PR's that relate.
Instead of qubits I will be researching with my time migrations from .NET Framework to .NET Core just to help this effort out here.
Any current thoughts here I know I sound like a broken record I just really need to see DNN version .NET Core as I like the CMS features. I can probably recreate all the modules I have and import the data I need. But I don't want to get off topic. I want to get more focused on this effort so I get a good idea of what will get accepted for a PR.