Current LoCo Contact(s) is not shown

Bug #496250 reported by Santiago Zarate
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
LoCo Team Portal
Fix Released
High
Daniel Holbach

Bug Description

LoCo Directory should display the name of the LoCo Contacts, either by entering it manually, or selecting a member from a combo box or so... using data in launchpad's team group...

Related branches

Revision history for this message
Efrain Valles (effie-jayx) wrote :

I can confirm this bug. We have discussed this before adn we havfe tried to fit the LoCo Contact figure in the LD, but since the Launchpad data structure for teams does not offer this info, we thought we would encourage teams to provide team ownership to the current loco contact, but since teams have more thant one loco contact this also fails.

We are currently open to ideas on how to solve this and we are willing to implement the idea that best captures the feeling of the world wide community.

Changed in loco-directory:
importance: Undecided → High
status: New → Confirmed
milestone: none → 0.1.1
Revision history for this message
Santiago Zarate (foursixnine) wrote :

In the particular case of Venezuela, curenly there are 3 LoCo Contacts, and i'm the team owner (And past LoCo Contact). A neat solution or a good one, as far as i can think, is to simply provide a combo box... with the lp team's members... if there are more than one LoCo, simply give the chance to add more... Also... providing a link for mail in loco-teams/loco-contacts mailing list, saying who is the new... can give a way to prevent fakes...

I'm not sure about the data model for the LoCo Directory... but this could be accomplished by using one of these django's csv fields... tho, not sure if it would be useful to have an history of the LoCo Contacts change.

Revision history for this message
Daniel Holbach (dholbach) wrote :

I think we should add a Boolean is_contact to the schema and add a small form where people can tick the check box... or something. This requires special though if there's a team set as an owner. This is not trivial.

Retargetting to 0.1.2.

Changed in loco-directory:
milestone: 0.1.1 → 0.1.2
description: updated
tags: added: schema-change
Changed in loco-directory:
status: Confirmed → Triaged
Changed in loco-directory:
milestone: 0.1.2 → 0.2.1
Michael Hall (mhall119)
tags: added: launchpad teams
Changed in loco-directory:
milestone: 0.2.1 → none
Revision history for this message
Daniel Holbach (dholbach) wrote :

This might be easier than I thought, but still requires a schema change.

Maybe we can just add something like this

contacts = models.ManyToManyField(TeamAdministrator)

and set limit_choices_to = {...}

summary: - Name of the current LoCo Contact(s) is not shown
+ Current LoCo Contact(s) is not shown
Michael Hall (mhall119)
Changed in loco-directory:
assignee: nobody → Michael Hall (mhall119)
Changed in loco-directory:
assignee: Michael Hall (mhall119) → Daniel Holbach (dholbach)
status: Triaged → In Progress
Changed in loco-directory:
milestone: none → 0.2.18
status: In Progress → Fix Committed
Changed in loco-directory:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.