B2G/Meeting/2016-09-27: Difference between revisions

Formatting
(Page generated from https://public.etherpad-mozilla.org/p/b2g-weekly-meeting by Special:ImportFromEtherpad)
 
(Formatting)
Line 7: Line 7:
* Meeting time: Tuesday, 9am Pacific / 4pm UTC
* Meeting time: Tuesday, 9am Pacific / 4pm UTC
* This week, we are '''back on Vidyo'''since last week's experiment was not very good
* This week, we are '''back on Vidyo'''since last week's experiment was not very good
<br />
Special meeting this week:<br />


Special meeting this week:
* [https://discourse.mozilla-community.org/t/b2g-os-announcements-on-tuesday/11041 https://discourse.mozilla-community.org/t/b2g-os-announcements-on-tuesday/11041]
* [https://discourse.mozilla-community.org/t/b2g-os-announcements-on-tuesday/11041 https://discourse.mozilla-community.org/t/b2g-os-announcements-on-tuesday/11041]
* [https://groups.google.com/forum/# https://groups.google.com/forum/#]!topic/mozilla.dev.fxos/FoAwifahNPY
* [https://groups.google.com/forum/# https://groups.google.com/forum/#]!topic/mozilla.dev.fxos/FoAwifahNPY
<br />
 
Attendees<br />
== Attendees ==


* Ari Jaaksi
* Ari Jaaksi
Line 31: Line 30:
* Many more on Vidyo and Air Mozilla...
* Many more on Vidyo and Air Mozilla...
<br />
<br />
Apologies:<br />
== Apologies ==


krz37 - will not be able to attend because I am traveling
* krz37 - will not be able to attend because I am traveling
* <br />


== Announcements ==
== Announcements ==
Line 40: Line 38:


* All B2G-related code is going to be removed from mozilla-central, the B2G community must fork Gecko if they want to continue. See the mailing list for the full announcement [https://groups.google.com/d/msg/mozilla.dev.fxos/FoAwifahNPY/Lppm0VHVBAAJ https://groups.google.com/d/msg/mozilla.dev.fxos/FoAwifahNPY/Lppm0VHVBAAJ]
* All B2G-related code is going to be removed from mozilla-central, the B2G community must fork Gecko if they want to continue. See the mailing list for the full announcement [https://groups.google.com/d/msg/mozilla.dev.fxos/FoAwifahNPY/Lppm0VHVBAAJ https://groups.google.com/d/msg/mozilla.dev.fxos/FoAwifahNPY/Lppm0VHVBAAJ]
<br />
 
== Q &amp; A ==
== Q &amp; A ==


Line 48: Line 46:
<s>Pad with questions:</s>[https://public.etherpad-mozilla.org/p/b2g-gecko-fork-questions <s>https://public.etherpad-mozilla.org/p/b2g-gecko-fork-questions</s>]
<s>Pad with questions:</s>[https://public.etherpad-mozilla.org/p/b2g-gecko-fork-questions <s>https://public.etherpad-mozilla.org/p/b2g-gecko-fork-questions</s>]
* Please put the questions in this pad so we can see them. Done
* Please put the questions in this pad so we can see them. Done
<br />
'''=== Questions from Vidyo ==='''


=== Questions from Vidyo ===
kgrandon - I guess we're removing all B2G specific bits from Gecko, going to be forking that. Have we thought naming, about Boot to Gecko or something else?
kgrandon - I guess we're removing all B2G specific bits from Gecko, going to be forking that. Have we thought naming, about Boot to Gecko or something else?
* Yes, the code is going to be removed.
* Yes, the code is going to be removed.
Line 79: Line 75:
* Agree that Mozilla was using this approach before the PWA term existed. That work will continue in Firefox.
* Agree that Mozilla was using this approach before the PWA term existed. That work will continue in Firefox.
<br />
<br />
'''=== Questions from Etherpad ==='''
 
=== Questions from Etherpad ===




Line 114: Line 111:
* Issue is that Gonk porting layers being removed
* Issue is that Gonk porting layers being removed
Is there a way to use libhybris to run full Linux stack and Linux port of Gecko, while converting all the phone-specific stuff to services?
Is there a way to use libhybris to run full Linux stack and Linux port of Gecko, while converting all the phone-specific stuff to services?
What does it mean for new Panasonic TVs? &quot;They concluded that Firefox OS TV was a project to be run by our commercial partner and not a project to be led by Mozilla&quot; is not very clear. Will Panasonic continue the development or will they stop using Firefox OS for future TVs?
What does it mean for new Panasonic TVs? &quot;They concluded that Firefox OS TV was a project to be run by our commercial partner and not a project to be led by Mozilla&quot; is not very clear. Will Panasonic continue the development or will they stop using Firefox OS for future TVs?
* That's up to them. We have certain business agreements. We can't comment on their longer term plan, they have a stable release they will use in 2.6. Whatever Panasonic wants to do is up to them and between them and Mozilla.
* That's up to them. We have certain business agreements. We can't comment on their longer term plan, they have a stable release they will use in 2.6. Whatever Panasonic wants to do is up to them and between them and Mozilla.
Line 133: Line 131:
* Growing area we want to be a part of.
* Growing area we want to be a part of.
could we boot to Gecko by using a striped down Android with only a fullscreen &quot;Firefox for Android&quot;?
could we boot to Gecko by using a striped down Android with only a fullscreen &quot;Firefox for Android&quot;?
in the future if we want to participate to Webapp/offline web app how can we get involved with Mozilla ?
in the future if we want to participate to Webapp/offline web app how can we get involved with Mozilla ?
* The PWA implementation in Firefox
* The PWA implementation in Firefox
So how to replace what will be missing after going out of gecko ? (I guess it's something that we will discuss in the community, sorry if it's irrelevant)
So how to replace what will be missing after going out of gecko ? (I guess it's something that we will discuss in the community, sorry if it's irrelevant)
<br />
<br />
'''Español'''
'''Español'''


¿Podemos tomar como base Chromium? Igual como hace Electron para crear desktop apps.
¿Podemos tomar como base Chromium? Igual como hace Electron para crear desktop apps.
Line 144: Line 143:




'''== David Wrap Up =='''
== David Wrap Up ==


We've tried to address the way communications have been made, have been cryptic, implications not always as visible as internally. Learning experience for us. Going to be harder for community to continue. We may not all agree on everything but have made it easier to have a conversation. We realise decisions are painful, part of why we wanted to get together today and work through so thank you. Look forward to continue working together going forward.
We've tried to address the way communications have been made, have been cryptic, implications not always as visible as internally. Learning experience for us. Going to be harder for community to continue. We may not all agree on everything but have made it easier to have a conversation. We realise decisions are painful, part of why we wanted to get together today and work through so thank you. Look forward to continue working together going forward.


'''== Ari Wrap Up =='''
== Ari Wrap Up ==


Looks like a cold-hearted business decision but there's an emotional side to this. A lot of effort people have put in. I wasn't part of this from the beginning but I can respect that. Dreams and hopes this could have been different but it wasn't. I want to look at this episode as first more engaged episode with community. First to admit communication could have been better but would not have changed the outcome. Going forward freedom and openness of the Internet important. No hesitation in my mind that one of unique values of Mozilla is the community. How do we learn from these episodes and make the best out the situations where not everyone agrees? Really appreciate the work people have done in the last months, in the platform. Keeping communication open. Emotional aspect part of the reality. Thank everybody. Recognise difficult to continue with codebase. Would be eager to see if new creative ideas come out of it, but realise it is hard.
Looks like a cold-hearted business decision but there's an emotional side to this. A lot of effort people have put in. I wasn't part of this from the beginning but I can respect that. Dreams and hopes this could have been different but it wasn't. I want to look at this episode as first more engaged episode with community. First to admit communication could have been better but would not have changed the outcome. Going forward freedom and openness of the Internet important. No hesitation in my mind that one of unique values of Mozilla is the community. How do we learn from these episodes and make the best out the situations where not everyone agrees? Really appreciate the work people have done in the last months, in the platform. Keeping communication open. Emotional aspect part of the reality. Thank everybody. Recognise difficult to continue with codebase. Would be eager to see if new creative ideas come out of it, but realise it is hard.
<br />
-------------&gt;8--- TEMPLATE ---8&lt;------------
'''B2G Weekly Meeting'''
* Date: 0000-00-00
* Host:
* Notes copied to the wiki each week [[B2G/Meeting]]
* Meeting time: Tuesday, 9am Pacific / 4pm UTC
<br />
Attendees<br />
* <br />
<br />
== Announcements ==
<br />
== Status Updates ==
=== Smartphone ===
=== Smart TV ===
=== Porting ===
=== Infrastructure ===
=== Documentation ===
=== Governance ===
=== Communications ==
=== QA ===
<br />
== Round Table ==<br />
Confirmed users
395

edits