I thought (assumed?) that what I had originally said was perfectly clear - but obviously it wasn't, so let me elaborate and be more explicit.
The DOEs will continue to work and will continue to be supported by me for all of the "standard" CoreRPG-child Rulesets available via the FG Updater utility. At this point in time (Feb-2018) this list of Rulesets consists of: CoreRPG, 3.5E, 4E, 5E, 13A (13th Age, ETA=Soon(TM)), CoC, CoC7, CnC, d20 Modern, Fate Core, Numenera, PFRPG and SW.
As SmiteWorks adds new Rulesets to the FG Updater / "standard list" then the expectation is that these new Rulesets will also be supported by me as far as the DOEs are concerned. This does depend upon a number of factors, including but not limited to me being provided a copy of the new Ruleset for testing purposes.
For any other Rulesets that the DOEs are currently supported for (in whole or in part) that support is being depreciated in preference to those Rulesets becoming child Rulesets of this new DORCore Ruleset. This should be a relatively minor change and code-clean-up for those effected Rulesets - provided, of course, that the Ruleset Dev would like his Ruleset Users to continue to have access to the functionality provided originally by the DOEs and now by the DORCore.
New Community Rulesets will also benefit from the functionality provided by the DOEs/DORCore by being developed as child-Rulesets of the DORCore.
I am happy to provide help to me fellow Community Devs to make their Ruleset a child-Ruleset of the DORCore, upon request - note that this is "provide help" not "do the work for them". To this end I am currently writing some API documentation to go along with the DORCore to make this as easy as possible, plus I am (almost) always available to answer questions, etc.
As new functionality is added to the existing DOEs and as new DOEs are developed the functionality they provide will be added to the DORCore at the same time, so that, for example, playing a game with the CoreRPG & DOEs will be exactly the same as playing a game with the DORCore - except, of course, that the DORCore also includes the Universal Die Roller (UDR) and a few extra Chat Box Slash Commands, etc, that the CoreRPG & DOEs do not have. Thus, it makes sense for new Rulesets to be developed as child-Rulesets of the DORCore - which was one of the design goals in the first place.
I am not taking anything away from anyone - everyone will still have access to whatever functionality they have right now and in some (most?) cases will actually end up having more functionality. What I am doing is shifting some of the workload from a single Dev and "spreading the work around" to a group of Devs and doing it in a way that will actually make it easier (I believe) for Community Devs to provide a Ruleset with a whole bunch of functionality right off the bat.
Everything I have ever done for this Community and everything I ever do has but one over-riding aim - to improve the RPG experience of those choosing to use FG and the REMs (Rulesets, Extensions & Modules) and other artifacts I produce. In fact there have been a few ideas and artifacts that I have submitted to SW which have been turned down and rejected (or put on hold), including a REM Updater that would allow Community Developed REMs to be pushed/pulled from a distributed virtual-repository in a way similar to the FG Updater - but even with these rejections and the time and effort "wasted" on them I have still been working for this Community. At no time have I ever (I believe) done anything to take away something I have provided to this Community (apart from perhaps taking a step backwards so as to ultimately provide a better way forward) - and I am actually quite hurt to think that there are those in this Community who would think that I would actually do such as thing, especially based upon my existing "track record".
I'll get off my soapbox now. </rant>