Community
Participate
Working Groups
For the general population, a "user information" page shows interesting bits of information about the user including (but not limited to): * Name * (optional) Picture; * (optional) biographical information; * Projects roles filled; and * Per-project activity, contributions via bugzilla (patches, comments) and authored commits in Git (for example). The general population should only be explosed to information about a user that is either already part of the public record (e.g. commit activity), or explicitly provided by the user for this purpose. For an authenticated user, their own page can show more information, including (but not limited to): * contact information (email address, phone, etc.); * organization affiliation history (which companies worked for and for what periods of time); * links to pertinent agreements (e.g. ICA/MCA); * ongoing elections that they need to vote in (committer, project lead, etc); * projects on which they are at risk of being identified as an inactive committer; and * other things that the user needs to know about I intend to use this bug as an umbrella bug for other content that will appear on this page, and use blocker bugs (subtasks) to provide detail on specific features.
*** Bug 258096 has been marked as a duplicate of this bug. ***
Drupal provides a user page that provides a lot of automatic stuff. We get a picture from Gravatar, for example. The PMI inserts some fields, like proposals and projects the user is involved in. The rest of the information doesn't really belong on the user page in Drupal. The "My Account" functionality is the right place for this (much of it is currently in the portal, but will be migrated to "My Account"). For one, some of the information is personal and private; we should avoid displaying personal and private information when we don't need to. If anything, the PMI should provide a link to "My Account". Given that we've implemented some of the functionality listed and the personal page is established, I'm going to resolve this bug FIXED. We can open separate bugs for additions that we feel strongly about.
