At the moment I don't have a plan, mainly because I didn't know that we'd need to refactor the STM core as much as we have had to.
I think that some other quite substantial changes are still needed to the F1 core, as the memory usage in global structures is far to high and is going to be very wasteful on the STM32F103R, V and Z series.
(its almost unusable on the VL series at the moment (STM32F100))
I agree we should probably refactor the L4 in the same way as the F103. I suppose we could do this now, as whatever changes are needed for the global vars issue could be applied later to the L4 core as they are independent of any restructuring
The code that was delivered by STM, was always split up into separate folders, e.g. a folder for the F103 and a folder for the L4, with duplicate copies of the HAL etc.
I have not compared the F1 HAL files to the L4 HAL, I presumed the files had different contents, even if the filenames where the same ???
STM seems to treat the HAL files for each MCU in isolation, e.g. from the STM32Cube you have to download each MCU series HAL separately, and they are not at the same versions.
I think whats important with the HAL files is to not modify them too much, as it makes it hard to update to a new version of the HAL if there have been extensive changes. And even small changes need to be documented and applied by hand to a set of updated HAL files.
Re: duplicate files in libraries
It may be possible to use git submodules to have linked folders e.g. for libraries into a separate "libraries" repo, but with the LibMaple repo I tried doing this and it didnt work, because 95% of people downloading from github, download via zip rather than running git and cloning the repo, and unfortunately github zip files to not contain the contents of the submodules, so people end up with empty folders.
So as the libraries are probably fairly stable, I think we'll probably have to live with duplicate files.
With core files, its currently hard to know how divergent they may become. As really we've only been looking at a small subset of the possible STM MCU series, F1, L4 and your own F4 trials.
(and I can't see a way to do this via submodules even if submodules didnt have the download via zip problem)
I think Wi6Labs will use some of the bug fixes etc from the F1 and L4, but I don't know if its in their remit to re-structure to match the new F1 structure.
I presume that we will need to restructure the code after its delivered by STM (Wi6Labs)
But I have no control over this - STM just let me know when they have something new to release.