To support the release of a new default configuration this year, we need to confirm the approach we will take for ensuring a smooth transition for users of the existing default config. Updating the default config with broader generic options will greatly reduce the support work currently requested for creation of custom configs.
Use cases:
A user with a v1 default config project updates Mapeo
Option to not rewrite the config if db !empty and no custom config present?
Users with a v1 default config project want to add a new project participant. New user installs Mapeo and has the same project key (MAPEO) but different categories.
Text in app + elsewhere to provide v1 config file and instructions for importing?
Todo:
Review the proposes changes, investigate how it will affect users, share thoughts with Programs team.
ximenabb
commented
2 years ago
Description: Logged in : https://www.notion.so/digidem/Ensure-backwards-compatibility-for-new-default-configuration-c32c530602b348538eae42a5382fd500 Details : https://www.notion.so/digidem/Feedback-on-Default-Config-v2-1eff17c2e8904d42bad65854b59f9683
To support the release of a new default configuration this year, we need to confirm the approach we will take for ensuring a smooth transition for users of the existing default config. Updating the default config with broader generic options will greatly reduce the support work currently requested for creation of custom configs.
Use cases:
Todo: Review the proposes changes, investigate how it will affect users, share thoughts with Programs team.