This most likely goes in Gemini or something but while I am thinking aobut it will post it here.

One thing I notice in DNN is that if there is some settings for personalization of a module settings per user the developer is having to develop an interface and provide a link to it in the module.  In general this gives a very inconsistent interface for DNN

(for an example look at the Forum module - editing your signature is done in the module but the edit profile link takes you to the profile page)

My suggestion is that DNN create an interface for the profile module/functionality much like the settings interface. So when I have a profile setting for a module (like the signature in the Forum module) it is given a specific control KEY when editing the module control. The profile module would then look and see if there are any controls with that specific KEY  for the modules that are on any pages. Then pull that control and present it as a tab in the edit profile link of the profile module.

I think would be a boon to module developers and to DNN overall.  On the UI side it would make DNN appear more 'tied together' and for developers it would give a more specific standard to use for user personalization controls.