Trying to make sure I understand:
The Fortress Fork Group (FFG) does not oppose development of an ECM/Fortress
adaptor for Merlin, or the development of migration tools for ECM/Fortress
users to Merlin, but does not promise to offer assistance in such
development. That is, such development would be left up to Avalon.
Is that right?
Yes.
The FFG just needs to continue on the fortress codebase in an evolutionary migration, not the revolutionary migration that switching the underlying container to Merlin would entail.
While switching to Merlin and its advanced capabilities will certainly be the choice that some users make, not everyone is in a position to switch containers, regardless of seamless component compatibility.
-pete
smime.p7s
Description: S/MIME cryptographic signature
