Gaia/SMS/Scrum/FxOS-S7

List of bugs

SMS issues handled by the SMS subteam (blocks the sprint bug 1202956)

Bugzilla link

Full Query

ID	Assigned to	Summary	Blocking b2g	Feature-b2g	Whiteboard	Resolution
818000	Julien Wajsberg [:julienw]	system messages are ignored if the handler pathname is not the same as the foreground application pathname	---	No cf_feature-b2g	[sms-sprint FxOS-S7 p=3][sms-sprint FxOS-S6 p=2][sms-sprint FxOS-S5 p=3]	WONTFIX
1180592	Steve Chung [:steveck]	[Messages][NG] mozMobileConnections shim Implementation	---	No cf_feature-b2g	[sms-sprint FxOS-S7 p=1][sms-sprint FxOS-S6 p=2]	FIXED
1198266		[Messages] Use ConversationService in the application	---	No cf_feature-b2g	[sms-sprint FxOS-S8 p=1][sms-sprint FxOS-S7 p=3][sms-sprint FxOS-S6 p=2]	WONTFIX
1201016		[Messages][NG] Migrate the current Message manager event handling to NGA	---	No cf_feature-b2g	[sms-sprint FxOS-S8 p=1][sms-sprint FxOS-S7 p=1]	WONTFIX

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

Remaining points and burndown chart

google chart api url for Sprint FxOS-S7

Burndown chart

	Remaining points
Start	8
Day 2	8
Day 3	7
Day 4
Day 5
Day 6
Day 7
Day 8
Day 9
Day 10
End

SMS issues handled by the SMS subteam outside of the sprint (contains whiteboard "sms-sprint-FxOS-S7")

No results.

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

All SMS issues tracked for this sprint (target milestone)

Bugzilla link

Full Query

ID	Assigned to	Summary	Blocking b2g	Feature b2g	Resolution
1184012	Stéphane Roucheray	[Messages] Throttle event handlers for the "input" event handlers	---	---	FIXED
1202956		SMS sprint FxOS-S7	---	---	INCOMPLETE

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

Sprint planning

Minutes are on a separate page.

Daily meetings

Day 2: 9th September

Steve

• bug 1179628 - [Messages][NG] Lay out Settings service structure
  • Start mozMobileConnections.
• bug 1180592 - [Messages][NG] mozMobileConnections shim Implementation
  • In review.
• bug 1201016 - [Messages][NG] Migrate the current Message manager event handling to NGA.
  • Have some discussion with Oleg about the possible layout for client.
• Reply some bugs that related to message app.

Today:

• Start some layout for message event handling.
• Clean up the review

Oleg

• bug 1176976 - [Messages][Drafts] Remove the draft saving/replacing action menu
  • No progress (in review).
• bug 1198266 - [Messages] Use ConversationService in the application
  • Trying updated bridge, couldn't make window-iframe communication work, looking into (in progress).
  • More profilings, had to build b2g by myself to get more info about setupShadowRoots, but results are controversial - data is different between runs, trying to understand what is going on.

Other:

• Started to look into "bug 1180592 - [Messages][NG] mozMobileConnections shim Implementation.";
• Finished reading my bugmail.

Today:

• Will handle review/feedback/need-info requests;
• Will work on review comments and assigned bugs.

Julien

• In PTO

Day 3: 10th September

Steve

• bug 1179628 - [Messages][NG] Lay out Settings service structure
  • Start mozMobileConnections.
• bug 1180592 - [Messages][NG] mozMobileConnections shim Implementation
  • r+ and waiting for green signal.
• bug 1201016 - [Messages][NG] Migrate the current Message manager event handling to NGA.
  • Working on the message clone first, maybe I will give a general clone for message since there is sms/mms for DOMMessage. In this way I might need to create a shim utils for clone method. Not sure if other shim will need clone(seems not except the DOMError).

(Oleg) Yeah, presumably only mozMobileMessageShim will need clone, btw do we have any updates on DOMError handling (in bridge I mean)?

(Steve) No from bridge as far as I know :/ But I don't want to push Wilson too much on this since there's lot of task waiting for him.

(Oleg) Heh, yeah, not that critical for us right now. He was also asking me about any news on gaia-fast-list, not sure if he reached out to you cause I don't know anything about it :)

(Steve) Oh I didn't catch up with the latest fast-list yet because the library changes frequently :p

(Oleg) Ah, okay, we can wait for more stabilized version first then.

(Steve) Yeah that's what I thought, I already tried out 2 different version of the fast-list, but maybe it's time to involve again after few weeks.

(Oleg) Okay, got it, thanks for the update! Maybe we can plan it for the next sprint.

• Clean up the review queue.

Today:

• Start some layout for message event handling.

Oleg

• bug 1176976 - [Messages][Drafts] Remove the draft saving/replacing action menu
  • No progress (in review).
• bug 1198266 - [Messages] Use ConversationService in the application
  • Created reduced test case and filed github issue for the problem I was facing: https://github.com/gaia-components/bridge/issues/83.
  • My WIP with auto switch to SharedWorker/alwaysLowered based services is moving forward (in progress).

    (Steve) Just discussed this with other folks yesterday, we thought that the service should be flexible for user to choose/switch between window/worker thread, not just service -> worker concept. So user can designate different context to init and switch the service context between both context seamlessly. Anyway we thought is good change if we can try out different combination.

    (Oleg) Yeah, it's kind of Manager that existed in the early bridge days, that can transparently change contexts/threads :)

  • Tried new bridge with sync window-to-window messaging - works quite well from the first look, at least faster than MessageChannel.
  • Was stuck with Gecko profiler that missed gaia-header related information, asked help from Ting-Yu, got reply - need to try again. Will file a bug to somehow lazy load gaia-headers in the meantime.

Other:

• Reviewed "bug 1180592 - [Messages][NG] mozMobileConnections shim Implementation.";
• Attended late NGA meeting on behalf of Julien.

Today:

• Will handle review/feedback/need-info requests;
• Will work on review comments and assigned bugs.

Julien

• In PTO

Day 4: 11th September

Steve

• There's a addon hackathon here, I didn't join the entire event but will still be a passer-by and voting for the result.
• bug 1179628 - [Messages][NG] Lay out Settings service structure
  • Start mozMobileConnections.
• bug 1180592 - [Messages][NG] mozMobileConnections shim Implementation
  • Landed.

    (Julien) I was so happy when I saw this bugmail :)

• bug 1201016 - [Messages][NG] Migrate the current Message manager event handling to NGA.
  • Have a quick patch about the message clong and message relay between different context. Still fighting with the init race condition and thinking about if it's possible that message missing while initializing the bridge and connection.

Today:

• Start some layout for message event handling.
• Feedback for conversation service.

Julien

• Just read/handled my bugmail and some of the other mails yesterday

Today: I want to:

• finish handling some more complicated bugmails and mails (eg: low storage stuff)
• handle review/feedback/NI queue
• work on the system messages issue

If all this moves forward well, I could:

• continue the prototype caching the thread list to a single db (including contacts/drafts/etc).

Oleg

• bug 1176976 - [Messages][Drafts] Remove the draft saving/replacing action menu
  • No progress (in review).
• bug 1198266 - [Messages] Use ConversationService in the application
  • Created WIP-for-your-feedback with ConversationService in window context with ability to upgrade to SharedWorker context (awaiting feedback).
  • Tried to leverage new sync bridge behaviour (window->window, window->iframe via dispatchEvent), but we have a race here - if client is created before service starts listening there is no connection is established, it doesn't happen with BC - will talk to Wilson if it's expected, if yes - we'll need to initialize window clients (that uses iframe service) once service is initialized. We don't have such cases yet, but I have one in my WIP patch.

    (Julien) Note that having a sync behavior kind of defeats the purpose of services; but if we use it only for the initial loading I think it's ok.

    (Oleg) Yep, I'd like to use for startup only and then upgrade to better "channel".

  • Retested alwaysLowered window and noticed significant improvement - we spend ~200-300 ms less to create that window - so filed a bug where we can seriously consider switching to it.

    (Julien) good, this is less a headache for us :) Do we know if it's automatically closing when the app's last window is closing?

    (Oleg) IIRC, yes, but we need more concrete/definite answer from Francisco or System app guys :)

    (Julien) OK; we'll also need to check how this behaves regarding the task manager.

  • Ting-Yu's advice with -e parameter helped to get more detailed profile.

Other:

• Filed bug for possible better handling of gaia-header;

Today:

• Will handle review/feedback/need-info requests;
• Will work on review comments and assigned bugs.