On Dec 16, 2013, at 06:28 PM, nicolas wrote:
The userProfile model in hyperkitty differs from the mailman's
I've noticed hyperkitty requires 2 extra fields (first name and last name)
when mailman3 only uses an optional one : "display name".
This causes confusion and unnecessary complexification of user's mapping and
imho these extra fields of hyperkitty :
- should not be mandatory just as in mailman
- might map exactly the mailman model (one field instead of two)
In general, Mailman core doesn't have much of a need for independent first and
last names (which also may be too limiting for certain people's names or
cultures). The "display name" corresponds exactly to the comment field in To
headers, and we'll just use it verbatim.
If Django is imposing a first/last name separation, then probably the best
thing you can do is just concatenate them for MMcore. You could possibly add
a hidden-by-default override field to let the user customize what would be
used in the core.