Gaia/New-Architecture-Program/Contacts/NGA SP3

General info

• Members
  • Borja Salguero (DEV)
  • Fernando Campo (DEV)
  • Jorge Prudencio (DEV)
  • Manuel Casas (DEV)
  • Alberto Villena (QA)
  • Maria Oteo (EPM)

• Meetings:
  • Daily happening everyday in Mumble at 10:30 CEST
  • Sprint Planning, on Monday (every two weeks)

• Links of interest:

Sprint objectives

• Finishing the code decouple from 'contacts.js', getting rid of any inter-dependency between views. Pending bugs from NGA S2 and adding more dependencies that we didn't include during last sprint.
• Initially we wanted to implement form.html and details.html as self-contained views completely in this sprint but the code is complex, there are a lot of conditions, so the idea is dividing the work in two steps: one basic and another more advanced that will include more dependencies and functionalities.
  • Edit view (form.html):
    • Basic part: NEW
    • Advanced part: UPDATE
  • Details view (details.html)
    • Basic part: OPEN (vcard and webcontact)
    • Advanced part: IMPORT (in case there is one contact, otherwise it goes to the contacts list)
• We need to study the code and make the decision of reusing it or refactoring. This last option makes sense but it can introduce more regressions.

Bugs for this sprint

• Pending bugs to be fixed in FxOS-S1 (26Jun) target milestone: https://goo.gl/bA49t7

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);

Demos

We want to have a demo in Whistler where these basic form (NEW) and details (OPEN) views can be shown. From Contacts list -> we can access to the details view using Manu's navigation prototype and going back to the list at the same point using back and former cache.

Pre-render cache can not be used as it has not been implemented yet.

Retrospective

Actions taken from last sprint

• As Raptor is not useful right now for integrating with Marionette 1169775 we need to:
  • AP1:Raise this issue in the NGA Program Management meeting and ask for deadline
  • AP2:In the meantime, we can try to add measures and print them with marionette.
• Development Synchronization is necessary: weekly meetings, or weekly mails so everybody is aware of the changes and progress in the NGA libraries.
  • AP3:Raise this issue in the NGA Program Management meeting. Done In Whistler it will be agreed the best way to do it with development team in charge of the NGA migration
    • We should open a follow-up task in next sprint to confirm that it happens after Whistler
• When landing the new code, we are not involving QA team or doing any type of regression tests, besides we should not forget the FTU part that also involves Contacts functionality (Importing, Merging)
  • AP4:We need to plan with QA team how to plan and handle all this work.
• AP5:Include a Contacts demo in the Agenda for Demo Sync Up meeting in Whistler (Tuesday in the morning) Done