Thank you for replying first, Andrew. You know, I am strongly committed to the vision of the UNA developper team.
What I learned so far, after approx. one year digging into community platform design (you are the architects, we are the designers) is, that whenever I am in online conferences with people I just learn to know, my mind starts flying around "what's her goals and how could she profit as my community platform member". I know, it's useless, but I cannot help it.
I found out, that the most demanding thing for me as a UNA community plattform designer, is assuming what's the best tools for my future community members to use, especially with potentially "concurring" modules/tools. For instance, I could eather use Groups mod for people with some kind of matching interests, or I could offer them the new Spaces mod, which could mean by far more options or, in a negative way, overwhelming my community members with too much functionality, when they just try to gather as a group with the same interest(s). Other examples are Discussions vs. Articles vs. Feed contribution (I know the difference, but you need to explain it to your community members first, in order to understand its usage) or E-Mail Messages vs. Text Chat, etc. I am sure, for you inventors of the UNA platform and for the majority of us, who dig into the world of the UNA CMS, concepts are clear. But, sometimes, even I get lost with concepts. Remember the Video Webinar, when you explained the new paid join and I watched the recording, and got lost in the difference between admin rights and group admin rights.
I would like to stress out your statement about too much functionality, that might people discourage from using a community platform. Keep it as simple as possible and give them tools they like to use.