WebDriver/RemoteProtocol/Meetings/2019/11/29: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(→‎PTO (🍂): ato away next Thursday)
(Add minutes)
Line 17: Line 17:


; Present
; Present
mmucci, whimboo, ato, maja_zf, AutomatedTester
; Regrets
; Regrets


== Minutes ==
== Minutes ==
=== puppeteer-alpha progress ===
mmucci reports that the we're in really good shape, ahead of schedule.
There is some slack built-up, which is good in case extra work comes up as we investigate.
==== Resources ====
* [https://docs.google.com/spreadsheets/d/169Wvq_NGcUJjPDeX_xPjffs6__tIlQDtKyemqlor3QI/edit?usp=sharing Dashboard]
* [[Remote/Milestones]]
==== Q&A about contingency, reserve ====
''[Starts at 00'03" in the recording.]''
=== Security review; shipping in Nightly ===
''[Starts at 00'09" in the recording.]''
* One of the concerns mentioned last week ("known unknowns") was the security review
** ato decided to declare the security review "done", since we've completed the follow-up work
that came out of the security review, and we're not aware of any additional work to be done.
We haven't heard back from the team doing the review, so ato has invited them to file follow-up
bugs if any additional concerns come up.
** In turn, the changes to make the remote agent actually ship in the Nightly channel have also
been submitted.
=== Fission update ===
''[Starts at 00'11" in the recording.]''
* whimboo and maja_zf met with ochameau to get advice on using JSWindowActors in the remote agent
** ochameau strongly recommends that we use JSWindowActors as soon as possible for our content work.
** whimboo has gotten ochameau's WIP patch working (https://phabricator.services.mozilla.com/D37690) and it makes certain things with frames easier.
Discussion about whether to proceed with this implementation now or later.
Concerns about have to rewrite a non-JSWindowActor solution in a couple of months, anyway.
=== Redesigning command-line flags ===
''[Starts at 00'24" in the recording.]''
Flags are confusing already, and we might want to bake in some flexibility in anticipation
of likely future use cases.
See bug comment for details about above concerns: https://bugzilla.mozilla.org/show_bug.cgi?id=1590830
=== Input from Logmein ===
''[Starts at 00'33" in the recording.]''
whimboo is going to get information about Puppeteer usage and priorities from Logmein.
The discussion will take place on a mailing list; subscription link has been
sent to the team.
Typically, we have one Mozilla-wide mailing list per external company.
=== Protecting internal methods ===
''[Starts at 00'35" in the recording.]''
Nothing prevents a client for using an "internal" method. We need schema validation
or a blacklist. For now, filter out underscore methods.
=== Decisions about MVP priorities ===
''[Starts at 00'51" in the recording.]''
Team members should feel free to decide what is high priority as they see fit,
as soon as new information comes to light. Update bugs accordingly.
No need to wait or ask for permission.
=== Collaboration Feedback ===
''[Starts at 00'54" in the recording.]''
Calling out pros (mostly) and cons of our new style of prioritizing and tracking work.
=== Discussion for next meeting: Q1 2020 ===
* Fission work
* Schema validation: initial planning in Q1. To be tackled later, possibly by an Outreachy participant. Likely in Rust, need to consider questions like dealing branching, backwards compatibility versus breaking changes, expanding the protocol.


== Recording ==
== Recording ==
Full recording of the meeting can be viewed here:
https://mozilla.zoom.us/recording/share/rmkbkR-JrV0E-BncHLtibxJIO2XVOkr3lYdfFpkDmZ-wIumekTziMw


== Actions ==
== Actions ==

Revision as of 16:56, 2 December 2019

Agenda

Roster

Present

mmucci, whimboo, ato, maja_zf, AutomatedTester

Regrets

Minutes

puppeteer-alpha progress

mmucci reports that the we're in really good shape, ahead of schedule. There is some slack built-up, which is good in case extra work comes up as we investigate.

Resources

Q&A about contingency, reserve

[Starts at 00'03" in the recording.]

Security review; shipping in Nightly

[Starts at 00'09" in the recording.]

  • One of the concerns mentioned last week ("known unknowns") was the security review
    • ato decided to declare the security review "done", since we've completed the follow-up work

that came out of the security review, and we're not aware of any additional work to be done. We haven't heard back from the team doing the review, so ato has invited them to file follow-up bugs if any additional concerns come up.

    • In turn, the changes to make the remote agent actually ship in the Nightly channel have also

been submitted.

Fission update

[Starts at 00'11" in the recording.]

  • whimboo and maja_zf met with ochameau to get advice on using JSWindowActors in the remote agent
    • ochameau strongly recommends that we use JSWindowActors as soon as possible for our content work.
    • whimboo has gotten ochameau's WIP patch working (https://phabricator.services.mozilla.com/D37690) and it makes certain things with frames easier.

Discussion about whether to proceed with this implementation now or later. Concerns about have to rewrite a non-JSWindowActor solution in a couple of months, anyway.

Redesigning command-line flags

[Starts at 00'24" in the recording.]

Flags are confusing already, and we might want to bake in some flexibility in anticipation of likely future use cases.

See bug comment for details about above concerns: https://bugzilla.mozilla.org/show_bug.cgi?id=1590830

Input from Logmein

[Starts at 00'33" in the recording.]

whimboo is going to get information about Puppeteer usage and priorities from Logmein. The discussion will take place on a mailing list; subscription link has been sent to the team.

Typically, we have one Mozilla-wide mailing list per external company.

Protecting internal methods

[Starts at 00'35" in the recording.]

Nothing prevents a client for using an "internal" method. We need schema validation or a blacklist. For now, filter out underscore methods.

Decisions about MVP priorities

[Starts at 00'51" in the recording.]

Team members should feel free to decide what is high priority as they see fit, as soon as new information comes to light. Update bugs accordingly. No need to wait or ask for permission.

Collaboration Feedback

[Starts at 00'54" in the recording.]

Calling out pros (mostly) and cons of our new style of prioritizing and tracking work.

Discussion for next meeting: Q1 2020

  • Fission work
  • Schema validation: initial planning in Q1. To be tackled later, possibly by an Outreachy participant. Likely in Rust, need to consider questions like dealing branching, backwards compatibility versus breaking changes, expanding the protocol.

Recording

Full recording of the meeting can be viewed here: https://mozilla.zoom.us/recording/share/rmkbkR-JrV0E-BncHLtibxJIO2XVOkr3lYdfFpkDmZ-wIumekTziMw

Actions

Status of Milestone 1

  • Last week: 63 Total; 47 Open (74.6%); 16 Resolved (25.4%); 0 Verified (0%)
  • This week: 75 Total; 50 Open (66.67%); 25 Resolved (33.33%); 0 Verified (0%); (including alpha-reserved)

Changelog

TBA

Work

Milestones
Development status of Puppeteer alpha
Puppeteer alpha dashboard
Bugzilla queries
All project work currently in development
Available MVP work
Completed MVP work
Bug overviews
Gutenberg dependency tree
Puppeteer examples dependency tree
Complete Puppeteer dependency tree
All ze boogs

PTO (🍂)

  • ato away Wednesday 27th November and Thursday 5th December
Retrieved from "https://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/Meetings/2019/11/29&oldid=1220817"