Projects are groups of or folders for repositories, which are currently implemented only for teams.

1. User needs to create a team with only her/himself as member. Call this a "proxy account," since this "team" will have only one member, and exists only to provide functionality to formerly-user repos.
2. User must manually transfer each of their repos from their own/user account to their proxy/team account. Note that users who are most likely to be interested in Projects are users with ... wait for it ... lots of repos.
3. Once a repo is transferred from a user account to her/his proxy/team account, the user effectively has 2 identities: "if [OP] follows a link to my user [account] (like the [ones in Issue comments]) they won't see my repositories. [OP] would have to know to look under [my user account>Teams]." If the user also belongs to real/non-proxy teams, the OP will need to "figure out which team I am using as a user-specific team."
4. Transferring a repo from user to team requires changing the repo URI, which means the user must change any links to the repo in any documentation. This is a huge hit for users who document their code for OP, and the hurt scales with number of repos to transfer.

Hence I request that Projects (repo folders) be made available for user accounts (not just team accounts), thus obviating the need to transfer repos to purely-proxy teams.

2016-01-23 edit by @dbennett

I'm going to remove labels from the description and title. We've already had problems mingling the two features on the initial request and there's no need for a pro-active complaint about something that's not even in design. For those interested in labels take a look at issue BCLOUD-11800 and comment / vote there if you'd like to influence the direction.