Repository navigation
Rearrange the ambassadors page and implement the "main contact" role #425
Description
Activity
I inspected the model.
User profiles belonging to the group 'ambassadors' are the current ambassadors.
Maybe we can extend with a role field (blank for normal users) and add a proprerty that check if this field is == 'main contact'
I also think we need a new free-text
rolefield.However, the main ambassador's flag should be separate, I think. This would leave us to specify something else in the
rolefield, if needed. I think that for the main ambassador, we can create a new group and use that as a "flag".I propose:
role = models.TextField(max_length=1000, blank=True) main_contact = models.BooleanField(default=0)The check would be (in pseudocode):
is_main_contact = 'ambassador' in User.groups and main_contactMaybe the check can be avoided if we make sure that only ambassardors are able to subscribe as main contacts.
@michelesr Note that users are marked as ambassadors manually via the admin. The main contact flag will be set manually via the admin as well.
I am okay with the proposed model fields. Not sure why you'd prefer a boolean flag instead of a group for the main contact flag, but I'm okay with that as well--it was also my initial idea.
The only thing is that the role field seems a bit too long to me, we're not supposed to keep that much info there. Maybe up to 255 symbols would be fine, but I'm also okay with a limit of 1000.
The only thing is that the role field seems a bit too long to me, we're not supposed to keep that much info there. Maybe up to 255 symbols would be fine, but I'm also okay with a limit of 1000.
Yeah, that's was only an example, limit can be set to 255 i guess.
@michelesr Note that users are marked as ambassadors manually via the admin. The main contact flag will be set manually via the admin as well.
Good. I'll start the implementation soon.
What needs to be done: