Voting starts in March for the Drupal Association Board election.
Updated: Comment #0
A follow-up to
In some edge cases you may need to refer to config or data even after a module in uninstalled.
Or, if you are a developer, you could migrate that config or data back in if you later re-install the module or install a related one that can use the same data. In comment #227 https://drupal.org/node/1199946#comment-7538503 it was suggested that core have a general backup/restore functionality. I don't know that we want to build that for core, but this could feed into a contrib solution for "unarchiving".
In addition, at least the option to archive config and/or data might take some of the fear out of having only the uninstall option.
When uninstalling a set of modules, provide default off option to archive configuration or tables. The tables can be discovered via hook_schema (e.g. archive by renaming them perhaps including the module's schema version instead of dropping them).
User interface changes
Added option for uninstall process. Needs perhaps help text and documentation.