Sigh, I've been really slack lately (curse you real life!) I don't have access to my laptop right now but from what I can remember I was working on the following:
ParticipantID (which is the address/user ID) First Name Last Name IsAdmin (boolean) I think we're going to need first/last names in there. Nicknames and avatars can be an optional extra. On email address, yes we should keep that. If we can replicate the email notification system from GWave it will go along way to helping push WIAB. James On Mon, Dec 13, 2010 at 9:08 AM, Nathanael Abbotts <nat.abbo...@gmail.com>wrote: > Those sound great, but I don't think we need "First Name". "Nickname" would > be much better, and more useful. > -- > Nathanael Abbotts > > > > On Sun, Dec 12, 2010 at 22:05, 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 >