Page Comparison

Maintain native KFS

New features are developed from KFS team

Sustaining team must maintain upgrade path.
What is the level of KFS expertise we must maintain on the sustaining team to do this?

May impact timeliness of new OLE features.

Do new features driven by financial system outweigh the cost of managing the upgrade path for the sustaining team?

Is the upgrade process lightweight enough to contract resources when required for the upgrades?

Fork from native KFS

No KFS upgrade path to maintain

Sustaining team must develop new functionality or merge contributed KFS code. What happens when KFS has to be upgraded to use JPA?

Desired KFS features may take longer to get.