-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathb2g-weekly-meeting
509 lines (244 loc) · 20 KB
/
b2g-weekly-meeting
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
T##$826B2G
Weekly Meeting
Date: 2016-09-27
Host: Ben Francis
Notes copied to the wiki each week https://wiki.mozilla.org/B2G/Meeting
Meeting time: Tuesday, 9am Pacific / 4pm UTC
This week, we are back on Vidyo since last week's experiment was not very good
Special meeting this week:
https://discourse.mozilla-community.org/t/b2g-os-announcements-on-tuesday/11041
https://groups.google.com/forum/#!topic/mozilla.dev.fxos/FoAwifahNPY
Attendees
Ari Jaaksi
David Bryant
Faramarz Rashed
Fabrice Desre
Ben Francis
George Roter
Kevin Grandon
Mattieu
ralf
Amit Kumar Jaiswal / @amit_gkp
Christophe Villeneuve / @hellosct1
Enrico
Jovan
gsvelto
Lapineige
Many more on Vidyo and Air Mozilla...
Apologies:
krz37 - will not be able to attend because I am traveling
== Announcements ==
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
== Q & A ==
Questions?
Pad with questions: https://public.etherpad-mozilla.org/p/b2g-gecko-fork-questions
Please put the questions in this pad so we can see them. Done
=== 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?
Yes, the code is going to be removed.
As long as it's not "Firefox OS", B2G is fine (Firefox is a registered trademark)
B2G/Boot to Gecko not trademarked, up to community if they want to keep that name or call it something else
But yes, you can argue that after the fork it is no longer "booting to Gecko"
mattieu - What will be the link be between the community and Mozilla Foundation regarding this potential fork?
I guess you're asking about Infrastructure. The infrastructure still exists. There will be a body of work in Gecko. As far as resources are concerned there won't be any resource investment from Platform Engineering or Connected Devices.
mattieu - On the Mozilla side, what are the next steps about Connected Devices and things like that?
We have a handful of projects going on. One is SensorWeb, one is Haiku... we will move to platform development but this is independent from B2G. We don't see those require a rendering engine or full whole home grown operating system. Connected Devices plans are not to use B2G or Firefox OS going forward.
mattieu - What makes the decision to drop everything now rather than last year?
Ari - We made the decision very early on to drop the commercial development of smartphones. During the spring there were several efforts to look into whether we can use B2G in Connected Devices. We wanted to finalise 2.6 for our TV partner and clean up the code so we had a stable release for them to go forward., Then the decision was made based on all the new work coming to Gecko that we would need B2G to fork. In Connected Devices we didn't find a reason to continue with B2G.
David - There were further investigations over the last 8 months to see what routes might be appropriate to take, after those months of investigation we felt we had a clear picture of what we planned to do, but in a way that follows through and puts the rest of the code base in the hands of the community
Will Mozilla continue to provide the B2G community with access to its infrastructure? For instance, Bugzilla, Taskcluster, Mercurial/Git hosting, MDN?
Infrastructure that's currently available is still available. Can continue to provide that in a self-supported model. They could decide to make changes which would be fine.
ralf - It would be interesting to hear if you guys think this forking is even possible? For me it feels like killing Firefox OS again. For me this is really now formally dead. Do you think there is a chance for this to survive, or could it maybe come together again with Servo for example?
Coming together is always a possibility. Impossible for me to anticipate what might be relevant in the 9 web engine parts of B2G. The right underlying engine for that work is a variable that's going to get looked at. E.g. purely embedding or headless.
Ari - It is far from being trivial, especially given there are no commercial products (e.g. getting hold of drivers). If you think of it as a phone operating system it's going to be very difficult (not impossible but very challenging, to be honest with you).
Fabrice - There are companies like Sony who provide a free open source base we can use.
David- Gecko is a large codebase, not that many people who deeply understand it. This creates significant challenges for the community. There are ways around those but non-trivial or require shifting infrastructure.
Ben - going to get much harder as codebases diverge. Not impossible but very hard.
David - There will be new components in Gecko that B2G may want to take advantage of so will require merging
Which parts of Gonk, Gecko, Gaia are going to be maintained by Mozilla?
None
ralf - B2G was the home for Progressive Web Apps as they are now called, long before this term was used. Do you have interest in supporting Progressive Web Apps? Now they are all dead even on the desktop.
We still think these technologies are important, and our involvement precedes Google's marketing around those terms. Also working on the web games stack and WebVR.
Agree that Mozilla was using this approach before the PWA term existed. That work will continue in Firefox.
=== Questions from Etherpad ===
Will Mozilla continue to provide the B2G community with access to its infrastructure? For instance, Bugzilla, Taskcluster, Mercurial/Git hosting, MDN? (and Discourse)
(see above)
Is B2G still considered Tier 3?
Yes, until it is removed.
I wonder why Mozilla announced transition & modified the architecture. They could have stated this earlier & stopped with 2.6 branch.
2.6 took until the summer. It took us a few weeks to put the announcement together. We were looking at whether products could be based on it or not.
Can Mozilla place all B2G-specifc code in a separate repo so that it's easy for B2G OS community to work on.
mozilla-central changes are going into mercurial. We will continue there.
There has been a mozilla-b2g/gecko-dev repo in the past, this could be re-instated
We're not taking on that activity but anyone else welcome
Is all Mulet-related code also affected by this? Of course, yes
Yes
Are latest B2G system apps are at least supported in the next Gecko? I heard that some of the new Rust code are coming to Gecko, but this means the core stack of B2G may need to be modified.
There's a steady stream of work relative to Gecko with use of Rust that have been proved through Servo. Most of those are internal that are beneath existing APIs.
For sub-pieces like the CSS engine we have for media decoding. May not be the case for webrender, very platform specific.
It's inherently the case these changes will have impact up the stack.
Steady stream of small changes happening even now.
Should we start to archive current B2G and Mulet source codes then start another new transition to be compatible with the next versions of Gecko, and even Servo? (But it be Boot to Servo at this time)
It's all in version control on GitHub. We can tag it.
Instead of a fork, will it be possible to have a stable interface on the C++ part to add and compile our part of code ? It will be easier for new C++ contributors to have a list of functions to use to add new camera functions for example than to search in Gecko fork code where add his code ( and worse to maintain when there is code modification in Gecko ... );
Why can't we have something like Gonk separate from the Gecko tree? Gecko has issues that prevents us doing that.
The history of Firefox OS was to develop it in such a way that that wasn't possible. Gecko doesn't expose a complete API surface. It could be possible in future but not today.
Due to the monolithic nature of Gecko it isn't currently possible to maintain those pieces out of tree.
Who took this decision, precisely? it would be (a little more) fair to talk with the community before or, at least, with your core developers (@Gabriel on the mailing list).
Consequence of a number of other decisions that got made about B2G and Gecko over the last nine months. Made by Mozilla Leadership within units of responsibility. It was Ari for Connected Devices and David Bryant for Platform Engineering, not a single person's decision.
When do you plan to do this remove of b2g code from gecko ? (= do we have time to manage what's next ?)
We have a number of activities that are queued up in the very near term, expect that to start later today.
So we don't have time to make a backup/archive (if needed ?)
So this project is going out of gecko. What are the plans on Mozilla Corp side ? Do you still want to help us in some way ? (This add a lot more work for the community, that is still quite small and not super experienced)
If we can use current Gonk build for later versions of Gecko, how about releasing some of B2G system apps (such as clock and calendar) as WebExtensions? If most of the B2G core is changed I prefer apps to be installed the same way as WebExtensions. As I mentioned in Telegram group I have forked "B2G" and "Gaia" in GitHub for archive and testing purposes.
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?
What does it mean for new Panasonic TVs? "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" 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.
question on telegram/irc: "What would be the basis for trust going forward with Mozilla after all this? Or does Mozilla see community involvement as less important in their next generation of plans?"
David - Community is constantly important as part of what we do. We work collectively on lots of things and independently as well. The community is ever and increasingly important to Mozilla and our next level of plans.
Beside from the FxOS specific APIs on which were still rely, which parts of B2G in Gecko would we still need for B2G to work?
Mostly the graphics and media stuff. Gonk widget layer and media rendering.
For the people like me (Matthieu) would it be possible to explain a bit more detailed what will have to be maintain (telephony stack, rendering engine, drivers..?) by the community as soon as B2G code is out of gecko ?
Gonk widget layer, media playback
Gonk back ends for several W3C APIs
Replacing legacy APIs with local web services (already planned)
Telephony stack is a big piece
Browser API will still exist
Camera API will go, maybe we can use MediaStreams? We take patches.
Input API
...
Does mozilla have any plan to provide a new embedded api of Gecko for applications like B2G in near future?
We have vaguely shared that embedding is an opportunity we are more interested in going forward. Putting web technologies in more places beyond the traditional ones.
Growing area we want to be a part of.
could we boot to Gecko by using a striped down Android with only a fullscreen "Firefox for Android"?
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
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)
Español
¿Podemos tomar como base Chromium? Igual como hace Electron para crear desktop apps.
There is no Gonk equivalent for Blink that renders web content directly to the lower levels of Android without the Android Runtime in between. You could theoretically create something like this, that would be a lot like Chrome OS!
== 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.
== 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.
------------->8--- TEMPLATE ---8<------------
B2G Weekly Meeting
Date: 0000-00-00
Host:
Notes copied to the wiki each week https://wiki.mozilla.org/B2G/Meeting
Meeting time: Tuesday, 9am Pacific / 4pm UTC
Attendees
== Announcements ==
== Status Updates ==
=== Smartphone ===
=== Smart TV ===
=== Porting ===
=== Infrastructure ===
=== Documentation ===
=== Governance ===
=== Communications ==
=== QA ===
== Round Table ==
Chat
krz37:18:21 I came here this week to know what was happening right now
krz37:18:21 thanks
krz37:18:21 in library
krz37:18:22 Thaknyou
krz37:18:22 see you
benfrancis:18:25 BTW, if there's a WebRTC based solution that you find that can support multi-person video conferencing then we could consider switching.
benfrancis:18:25 Vidyo is what Mozilla uses internally so is the default choice
Lapineige:18:26 Jitsi Meet ?
benfrancis:18:28 Never used it, does someone need to host that?
Lapineige:18:29 we can host it, but their offer a free instance creation at meet.jit.si
Lapineige:18:29 I used it a lot with group conversation (2~5), it's working fine
benfrancis:18:30 cool
Lapineige:18:30 it should work fine with big groups, as it is not CPU-hungry
Lapineige:18:31 why not trying it for next meeting - and switching back to vidyo if it doesn't work ?
Jamie:18:32 Bug number added
Lapineige:18:32 thx :)
kskarthik:18:55 appear.in also nice
Luca:10:09 Lapi, Jitsi Meet seems a great solution!
Lapineige:10:43 We should warm someday that we try it during the next meeting. We can't just say it at the beginning of one meeting (we might loose some people).)
Lapineige:10:43 I had no time to do it, sorry :/
jamie:18:02 sorry i cant be in vidyo right now, im sitting in class right now
Lapineige:18:04 ok np
jamie:18:05 any news on any of those bugs?
Lapineige:18:06 no
jamie:18:06 i might be working on our gecko bug later on today
Luca:18:09 Lapiniege, cuold you please share the Vydio room link?
Luca:18:09 could*
Lapineige:18:10 https://v.mozilla.com/flex.html?roomdirect.html&key=2FCZj4WaeeMQ
Lapineige:18:37 Hi Jovan
Lapineige:18:37 do you news about this blocking bug ?
eyome:20:59 Hi
eyome:21:00 If it could help, I tried https://vroom.im/ several time and it works well
eyome:21:01 the plus of vroom iis the add of a collaborative pad (etherpad)
eyome:21:01 I think it's interesting for a collaborative project
Enrico:21:29 I won't be at the meeting on 13th unfortunately, but I added the progresses with the E3 porting to the pad.
Enrico:11:12 and some other topics I think could be of interest
Luca:13:18 Added some notes
krz37:17:57 Hey, joining the room soon! a bit late sorry
jamie:18:05 im in class so right now i can use mic
jamie:18:06 *can't
m.ducorps:18:07 i think lapineige is off for 1 month or 2
jamie:18:09 what components are now up and running and what is the status of our gecko bug?
jamie:18:09 sorry having issues with vidyo
m.ducorps:18:19 yeah skype did work
m.ducorps:18:19 i'm using now
jamie:18:20 please just see if you can get some andswers to my questions in QA section
jamie:18:20 if im going to start putting a QA department back togther i need a few basic things to start now that we have some stuff to test
krz37:18:40 Thank you everyone!
krz37:18:40 jamie, is everything ok on your side?
m.ducorps:18:05 @luca you are with us ?
krz37:18:07 btw, I cannot really write this week on the pad because I am really slow because of this
krz37:18:07 on my arm
krz37:18:09 Hi benfrancis :)
Jovan:18:10 sorry guys my connection is not really well right now, can someone else continue?
Luca:18:10 I'm just following from the pad! :)
Luca:18:10 Hi guys!
krz37:18:36 some magic happened with Vroom and I am alone in the room
krz37:18:36 what about you guys?
krz37:18:36 are you still there ?
m.ducorps:18:36 yes
m.ducorps:18:37 i'm with novski
krz37:18:37 that's pretty weird, I will re-attempt in a few mins
m.ducorps:18:41 okey lost etherpad also
krz37:18:42 back
krz37:18:43 but I am still in a parrallel room alone
krz37:18:43 can you see me?
m.ducorps:18:43 nop
m.ducorps:18:43 you've logged back in ?
krz37:18:43 I guess I will follow here then
krz37:18:43 yes
krz37:18:44 10 times now
krz37:18:46 So I guess we should go back to Vidyo next week
krz37:18:58 m.ducorps, we need to clarify the bullets added to the Documentation part
krz37:18:58 We give one more week and if there is no feedback about it we'll just go ahead and do the modification we've proposed in the etherpad
krz37:18:58 it is about the wiki right?
m.ducorps:19:00 it7s about the documentation in general
krz37:19:00 when the meeting is over, please write here also, I will put the notes to the wiki
krz37:19:00 alright :)
m.ducorps:19:00 we don't want to wait for contribution for to long
m.ducorps:19:01 do you know where to find the doc to do a gecko patch ?
krz37:19:02 no sorry, only pushed to gaia
m.ducorps:19:02 i got this from gerard majax
m.ducorps:19:02 Can you also provide a Gecko patch that updates the sha1 in b2g/config/aries/sources.xml and b2g/config/nexus-5-l/sources.xml for the Gaia project ? There should be docs about how to do your first Gecko patch and submit this via MozReview :)
krz37:19:03 probably on MDN
krz37:19:03 ask him for more details
krz37:19:03 I am not yet working on gecko
krz37:19:03 becuase I have a reasearch conference next week and only after I can be free
krz37:19:04 so I won't be able to attend here either next week, not sure where I will be at this time in St. Petersburg
m.ducorps:19:05 lol okey
m.ducorps:19:05 yes i'l ask him within the bug
krz37:19:06 but I will post on Discourse for the weekly meeting and update about switching back to Vidyo
krz37:19:08 meeting over?
krz37:19:22 creating the meeting notes for next week
krz37:19:58 updating the wiki
Lapineige:15:00 thanls :)
Lapineige:15:01 thanks*
Reinhart:18:12 Any of the questions answered?
Thatoo:20:08 zut, j'arrive après la bataille.
Thatoo:20:29 zut, j'arrive après la bataille.
Thatoo:20:31 Sorry, I've been anavailable these last month but this news made me coming back to see what's going on. I'm so sorry to discover that.
Xia:10:04 Hello?