According to this answer,
.local .cache and
.config are, by convention, configuration storage locations adopted by Gnome and Ubuntu.
.gnome .gnome2 and
.gconf therefore legacy configuration directories, or are they supposed to co-exist?
And does the adoption of dconf alter these dot-file application config conventions?
Finally, what is the relation of the gconf-editor data settings to these directories? Do .gnome/.gconf contain the same info that gconf-editor accesses?
Updates: XDG has been pointed to as the reason for .cache, .local, and .config.
GNOME technology used to store application settings. [...] dconf is the GNOME3 replacement for gconf which has not been maintained for some time. dconf is also expected to bring performance improvements over gconf (relevant for applications startup).
I expect, based on that that there will be a somewhat anarchic migration path from gconf settings to dconf. I would love to hear any additional perspectives.