| 2011-01-28 19:03:12 |
Christopher Adams |
bug |
|
|
added bug |
| 2011-01-28 19:03:55 |
Christopher Adams |
ppl: importance |
Undecided |
High |
|
| 2011-01-28 19:03:55 |
Christopher Adams |
ppl: milestone |
|
0.2 |
|
| 2011-01-28 19:03:55 |
Christopher Adams |
ppl: assignee |
|
Brad Phillips (brad-bradphillips) |
|
| 2011-01-28 19:21:48 |
Christopher Adams |
description |
Each private profile page will have a button to make the profile public or private.
If the owner makes the profile public, the form must check if the user has a value set for the username field in aiki_users. (Recall that when users are created they are not assigned a username).
If the user does have a username, then the profile is published successfully.
If the user does not have a username, the owner must choose a username for the user. When the owner pushes publish, a text field labeled "Username:" will appear. The owner must enter a unique username in that field before he or she can publish the profile.
Extra:
If the username is not unique, the owner should see a meaningful error and be able to choose a new name.
If the user navigates away from the page before choosing a username, then nothing should happen. The profile should not be published. |
Each private profile page will have a button to make the profile public or private.
If the owner makes the profile public, the form must check if the user has a value set for the username field in aiki_users. (Recall that when users are created they are not assigned a username).
If the user does have a username, then the profile is published successfully.
If the user does not have a username, the owner must choose a username for the user. When the owner pushes publish, a text field labeled "Username:" will appear. The owner must enter a unique username in that field before he or she can publish the profile.
Essential:
The form must constrain the allowed username:
* Only alphanumeric characters [A-Z] [a-z] [0-9].
* Usernames cannot be more than 25 characters. (Up for debate. Twitter is 15.).
Extra:
If the username is not unique or the right format, the owner should see a meaningful error and be able to choose a new name.
If the user navigates away from the page before choosing a username, then nothing should happen. The profile should not be published. (Please test this!)
|
|
| 2011-02-10 22:47:01 |
Christopher Adams |
ppl: status |
New |
Confirmed |
|
| 2011-02-12 15:36:53 |
Christopher Adams |
ppl: importance |
High |
Critical |
|
| 2011-02-13 17:01:03 |
Christopher Adams |
ppl: milestone |
0.2 |
0.3 |
|
| 2011-02-13 17:01:27 |
Christopher Adams |
summary |
When a profile is set to public for the first time, the owner must set a username for that user |
When the owner invites a user, the owner must set a username for that user |
|
| 2011-02-13 17:04:34 |
Christopher Adams |
description |
Each private profile page will have a button to make the profile public or private.
If the owner makes the profile public, the form must check if the user has a value set for the username field in aiki_users. (Recall that when users are created they are not assigned a username).
If the user does have a username, then the profile is published successfully.
If the user does not have a username, the owner must choose a username for the user. When the owner pushes publish, a text field labeled "Username:" will appear. The owner must enter a unique username in that field before he or she can publish the profile.
Essential:
The form must constrain the allowed username:
* Only alphanumeric characters [A-Z] [a-z] [0-9].
* Usernames cannot be more than 25 characters. (Up for debate. Twitter is 15.).
Extra:
If the username is not unique or the right format, the owner should see a meaningful error and be able to choose a new name.
If the user navigates away from the page before choosing a username, then nothing should happen. The profile should not be published. (Please test this!)
|
Each private profile will have a button that lets the Owner invite that People to the site.
At this point the owner must choose a username for the user. When the owner pushes Invite, a text field labeled "Username:" will appear. The owner must enter a unique username in that field before he or she can publish the profile.
Essential:
The form must constrain the allowed username:
* Only alphanumeric characters [A-Z] [a-z] [0-9].
* Usernames cannot be more than 25 characters. (Up for debate. Twitter is 15.).
Extra:
If the username is not unique or the right format, the owner should see a meaningful error and be able to choose a new name.
If the user navigates away from the page before choosing a username, then nothing should happen. The invitation should not go through. (Please test this!)
Ideally we ewant:
1) Owner imports user
e.g.: Jon Phillips, http://twitter.com/rejon
2) Owner invites user to the site
There will be some kind of invite button on the profile page
3) Owner is asked to choose username for the user
e.g.: rejon
4) PPL checks the username is valid
5) PPL sends an email to the user with an invite code
6) Person now has a permalink
e.g.: [root]/people/rejon
Is (6) possible or do we have to accept [root]/people/((userid))/((username))
? |
|
| 2011-02-21 06:37:57 |
Christopher Adams |
ppl: importance |
Critical |
Undecided |
|
| 2011-02-21 06:37:57 |
Christopher Adams |
ppl: status |
Confirmed |
Invalid |
|
