Opened 14 years ago

Last modified 12 years ago

#93 new task

Consistent terminology for people

Reported by: adehnert Owned by:
Priority: normal Milestone: Sometime
Component: People Version:
Keywords: Cc:
Size: medium

Description

Through the code (and probably the UI) we use "people", "officer", "signatory", and maybe some other terms to describe the president, treasurer, and other OfficerRoles?. We should pick one consistent terminology and use it.

Change History (1)

comment:1 Changed 12 years ago by adehnert

I'm moving towards standardizing on "people". I made significant additional progress on the "Update people" page today with commits a7c08e427586eb870ba45df5718f4603365b244c and 53e624e1ae8670b0a0323ddfa6d0a25a62485aa3:

commit a7c08e427586eb870ba45df5718f4603365b244c
Author: Alex Dehnert <adehnert@mit.edu>
Date:   Wed Jun 5 07:24:45 2013 -0400

    Change "Update people" URL to say "people"
    
    It had said "officers", which was inconsistent with the terminology used
    elsewhere on that page.
    
    This also adds a redirect from the old URL. The redirect view used is custom
    and I *think* should work, but I'm not sure. Django doesn't appear to have
    something built-in for this;
    https://docs.djangoproject.com/en/dev/ref/class-based-views/base/#redirectview
    doesn't seem to support view names.

commit 53e624e1ae8670b0a0323ddfa6d0a25a62485aa3
Author: Alex Dehnert <adehnert@mit.edu>
Date:   Wed Jun 5 07:22:27 2013 -0400

    More consistently use "people" in the UI
    
    Avoid using "officer" or "signatory" in the "Update people" UI, in favor of
    "people". This is a partial fix for ASA-#93 that mostly gets that page into
    good shape.
Note: See TracTickets for help on using tickets.