1035255 - [Telcel] Split calls from a conference call

Status: RESOLVED DUPLICATE of bug 909236

(Firefox OS Graveyard :: Gaia::Dialer, defect)

Description

[Vance Chen [:vchen][skype:vance.lucida][[e-mail]]]

>> Feature Request Title:
[Telcel] Split calls from a conference call

>> Description of feature, or problem to be solved
The conference call feature is introduced in FFOS since 1.2. However, till 2.0 FFOS doesn't provide a way to split call from conference call(Can only hang up the call, but cannot split the call from the conference call to become an separate call again)

>> Impact of implementing the feature/solution
Can enhance the usability of conference call feature, also Telcel/AMX is asking for this feature.

>> Impact of NOT implementing the feature/solution
Reduce the usability of conference call feature

>> Date required
Prefer to have this feature in FFOS 2.1

Comment 1

[Vance Chen [:vchen][skype:vance.lucida][[e-mail]]]

Hi Wesley, Wilfred, is it possible we can put this new feature request into 2.1 scope?

Thanks

Vance

Comment 2

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

AFAIK, this falls into COMMS team. 
Current feature set for 2.1 is quite big for the team, so I would say let's put it in 2.2.
I'll leave the call to Wilfred.

Comment 3

[Wilfred Mathanaraj [:WDM]]

this work is a quite large  - we will not be able to do this in 2.1

before we put it into any release I would like to work with UX and eng to understand what capabilities we have and how big this item is going to be (rough estimate) - I also expect some RIL work here.

Comment 4

[Doug Sherk (:drs) (inactive)]

I don't think this would be very difficult from the Gaia side. Rough estimate is that it would take 3-4 days of man hours for the changes to the dialer app. I can't speak for the RIL side of this though and I suspect it would be more difficult for them.

Comment 5

[Anthony Ricaud (:rik)]

I think it is a bit more complicated than it looks because of the edge cases.

When you unmerge someone, do you stay on the conference call or do you switch to that call?
When you have one conference call and one regular call, we can't unmerge someone else (we have a maximum of two "lines" opened). Do we remove the buttons, do we show an error message?

So I wouldn't commit to it without nailing down the UX first.

Comment 6

[Doug Sherk (:drs) (inactive)]

None of those things would really change the development cost. They're just things that you have to factor in when doing any feature work.

Comment 7

[Doug Sherk (:drs) (inactive)]

Also, note that my estimate isn't a commitment. We shouldn't be so scared of giving estimates that we just don't. It helps other departments arrange their schedules and make decisions when they know roughly how expensive work will be. The only thing we will ever commit to is "we'll get it done for this branch's FC/stabilization date", and even then we sometimes don't and the world doesn't end.

Comment 8

[Wilfred Mathanaraj [:WDM]]

Doug/Rik - thanks - none of your estimate is taken as a exact value - we wont know until we look further as to what work is involved

Comment 9

[Hsin-Yi Tsai (she/her) [:hsinyi]]

(In reply to Doug Sherk (:drs) from comment #4)
> I don't think this would be very difficult from the Gaia side. Rough
> estimate is that it would take 3-4 days of man hours for the changes to the
> dialer app. I can't speak for the RIL side of this though and I suspect it
> would be more difficult for them.

Gecko is ready :)

(In reply to Anthony Ricaud (:rik) from comment #5)
> I think it is a bit more complicated than it looks because of the edge cases.
> 
> When you unmerge someone, do you stay on the conference call or do you
> switch to that call?

From the spec point of view, "someone" is split out of the conference call but others remain staying.

> When you have one conference call and one regular call, we can't unmerge
> someone else (we have a maximum of two "lines" opened). Do we remove the
> buttons, do we show an error message?
> 

Just share that Gecko will deliver "removeError" message to gaia. But still depends on how our UX is

> So I wouldn't commit to it without nailing down the UX first.
> 
> *** This bug has been marked as a duplicate of bug 909236 ***

Comment 10

[Carrie Wang [New account: [e-mail]]]

My estimation is that UX is not too difficult, but since we only have one week before implementation, I'm not sure we can commit it for 2.1.

Comment 11

[Wilfred Mathanaraj [:WDM]]

this is definitely not for 2.1!

i am trying to find out which release we can plan for.