Closed Bug 997400 Opened 10 years ago Closed 10 years ago

[signup] Create a vouch model

Categories

(Participation Infrastructure :: Phonebook, defect)

2014-07.3
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: hoosteeno, Assigned: sancus)

References

Details

(Whiteboard: [vouching rel. 1])

As part of the signup refactor, we need to build a vouch model in the application. Specs:

* voucher and vouchee each can have many of these

* field "description" populated on save with value from textarea
  ** 500 char max
  ** subset of markdown allowed (same as in bio field on profile)
  ** needs some custom helptext. Suggestion: "When you vouch someone, you're saying that you believe their contributions to the Mozilla project are so significant that you will support their inclusion in the Mozillians directory ([read more about vouching]). In this field please enter the reason you are vouching this person. Please include links to relevant contributions." 
  ** voucher can only create vouch descriptions, not edit

* field "vouch_date" populated on save

* field "voucher" populated on save -- relates to userprofile of voucher

* field "vouchee" populated on save -- relates to userprofile of vouchee

* admin can edit description via /admin 

* admin can create/delete vouches via /admin
See Also: → 997451
Additional spec:

* all accounts are limited to 6 vouches total
Assignee: nobody → sancus
Whiteboard: [vouching rel. 1]
Status: NEW → ASSIGNED
Version: other → next
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Verification steps listed in comment #0 and comment #1. Also note that some of the functionality described here was resolved in other bugs (bug 1033420, bug 1033298)
Verified the following:
1. 500 character max in field "description"
2. Custom help text explaining what vouching means
3. Some markdown allowed (I was able to make bold text)
4. User cannot be vouched more than 6 times
Bumping to verified per comment 4. Thanks for the solid testing, terrameijar!
Status: RESOLVED → VERIFIED
Version: next → 2014-07.3
You need to log in before you can comment on or make changes to this bug.