Given available resources and release timeline, there will be time for @zmike to focus on only one of these tasks. Here is some background on the potential options:
**Settings:** The settings infrastructure for Enlightenment is, in a word, bad. There are a nearly infinite amount of settings dialogs full of [[e_configuration_options_compendium/|externally-documented]] options; options which, in many cases, make almost no sense in the context of the dialog they reside in. This is a huge hassle both for experienced users (eg. me) as well as newcomers, and it is one of the most complained about aspects of the user experience. Rewriting this will be a substantial task, but the result will provide a more sensible user experience for the hundreds of available configuration options.
**Gadgets:** The gadget subsystem(s) in Enlightenment was organically developed over a period of 10+ years. The API is completely nonsensical, very hostile and unfriendly to new developers, and extremely difficult to use. Gadget-related bugs are the second largest category of reported issues, surpassed only by the jenga-like filemanager subsystem. Rewriting and improving this will allow for redesigning of existing gadgets as well as providing an API which facilitates more rapid integration of new gadgets, potentially even in non-C languages.
The less-voted-for option will become the focus for E22 development provided that a more urgent issue has not arisen.