Proposed changes to the “Remote Protocol” and "Testing :: Marionette" components

Hi all,

After the JavaScript code (server side) of Marionette has been moved a
while ago from “testing/marionette” to “remote/marionette” only the
Marionette Python client and harness remains under the former location.
To ease the handling of core Marionette issues and to align the Bugzilla
components to the actual source location in mozilla-central I want to
propose the following changes:

Move “Testing :: Marionette” to “Remote Protocol :: Marionette”

Move the component and continue using it for the Gecko side
implementation of the Marionette protocol.

Owner: Henrik Skupin
Peer(s): James Graham, Julian Descottes, Alexandra Borovova
Source Dir(s): remote/marionette
Description: Marionette is a remote protocol that lets out-of-process
programs
communicate with, instrument, and control Gecko-based browsers.
Combined with geckodriver, this forms our WebDriver classic
implementation.

Create “Testing :: Marionette Client and Harness”

Create a new component for the Marionette Python client and harness to
cover internal testing issues like test packaging and execution. The
owners and peers will be identical to the “Remote Protocol ::
Marionette” component.

Owner: Henrik Skupin
Peer(s): James Graham, Julian Descottes, Alexandra Borovova
Source Dir(s): testing/marionette
Description: Python client and harness for the Marionette remote protocol
implementation.

Also I’m pleased to announce that Alexandra Borovova (Sasha) will be
promoted as peer for all components of the “Remote Protocol” product
including the new “Testing :: Marionette Client and Harness” component
after having contributed numerous patches and reviews to the Remote
Protocol codebase.

Further I also want to add James Graham as peer for these components
given that he has been actively working on both WebDriver specifications
and our implementations for quite some time, but we somehow missed
nominating him officially as a peer.

Please let me know if you have any suggestions or concerns. Absent any,
I will go ahead and implement the changes via bug 1794552 [1].

Thanks
Henrik

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1794552

--
Henrik Skupin
Staff Software Engineer
Mozilla Corporation

Henrik Skupin wrote on 06.02.23 15:25:

All the changes were completed in
https://bugzilla.mozilla.org/show_bug.cgi?id=1794552.