I would say profiles should *at least* have: - address/ID - real name (could be split into first, middle, last) - display name - image/avatar (where it must be hosted can vary--the image will have *some* URL either way)
In addition, I think some of these might be good to have: - status message - e-mail address(es) Some other possible ones (these would probably not be part of the standard, but instead depend on the wave provider): - phone number(s) - website(s) On Sun, Dec 12, 2010 at 17:28, Michael MacFadden < michael.macfad...@gmail.com> wrote: > These are all great ideas, for this thread, I am mainly just looking for > what fields we think we should have in the User Profile. I think we will > have separate threads on privacy controls, permissions and security, etc. > > For privacy for the initial pass, I will assume that everything is private > and nothing is shared with other users other than your user id and avatar. > > Still wondering if Nickname / Display name is different than your User Id? > > ~Michael > > On Dec 12, 2010, at 2:23 PM, Tad Glines wrote: > > > I think a separate profile store would be more flexible. This separates > the > > user authentication, from user profile. > > The user should also be able to configure visibility of profile > information. > > At a minimum, I think the user should be able to choose which fields of > > their profile they want to be public (with private being the default). > > > > I also think the user should be given a "Display Name" field that > > is separate from their real name. We should probably also provide the > > ability for a server admin to specify which profile values are "required" > > during registration and profile update. > > > > -Tad > > > > On Sun, Dec 12, 2010 at 2:05 PM, Michael MacFadden < > > michael.macfad...@gmail.com> wrote: > > > >> All, > >> > >> I am thinking of adding some functionality around user profiles. There > are > >> two main thrusts in the functionality. The first is implementing some > user > >> account / profile API with some sort of pluggable architecture such that > the > >> account profiles could be hooked up to an organizations exiting user > store. > >> The second would be implementing a basic self contained instance for out > of > >> the box functionality. > >> > >> The question I have for every one is what information should be in the > user > >> profile. Right now all we have in the Profile API is: > >> > >> - Address / User Id > >> - First Name > >> - Full Name > >> - Avatar Image URL > >> > >> > >> I was thinking that to start off we would have: > >> > >> - User Id > >> - First Name > >> - Last Name > >> - External Avatar Image (link to an external image) or > >> - Internal Avatar Image (image uploaded by the user) > >> - Email Address (assuming we still want email integration) > >> > >> Along the way, I would be adding a "My Account" or "My Profile" page. > Just > >> looking for some design input. Thanks. > >> > >> ~Michael > >
