That sounds great, and I agree with you.
So then, let's go ahead with a sub-module within the Testing
Infrastructure module
The owners of the sub-module will be: James Lal <lightsofapollo> and
Gareth Aye <gaye>.
The peers of it will be: Ghislain Lacroix <auswerk> and Mike Pennisi
<jugglinmike>.
If we don't hear any objections (now is a good time to speak up) then
we'll make this official on Monday August 12 and I'll update the wiki on
that day.
Thanks,
Clint
On 8/6/2013 7:26 PM, James Lal wrote:
Human interface failure!
Hey Clint,
This looks good to me (and thanks for guiding us through this process) - I see
some other modules have multiple owners ? If we are still doing that I would
like to clarify that Gareth should be listed there too.
Owners: :lightsofapollo, :gaye
I would like to note we volunteered jgriffin here- I am 100% ok with this but
if your on the peer list that effectively means that your responsible for
reviewing code (and having some time/headspace for the project). I would amend
this list to a slightly shorter list initially:
Peers:
- Ghislain "Aus" Lacroix <auswerk>
- Mike Pennisi <jugglinmike>
Then add people as they are sure they have time/interest to maintain the
project long-term. I am in no way trying to block people from getting involved
but I don't want to block time off from people without their consent.
- james
----- Original Message -----
From: "James Lal" <[email protected]>
To: "Clint Talbert" <[email protected]>
Cc: "Gareth Aye" <[email protected]>, [email protected], [email protected],
[email protected], "Dylan Oliver" <[email protected]>, [email protected], [email protected],
[email protected], [email protected]
Sent: Tuesday, August 6, 2013 7:20:38 PM
Subject: Re: Proposal for addition of a new testing module
Hey Clint,
----- Original Message -----
From: "Clint Talbert" <[email protected]>
To: "Gareth Aye" <[email protected]>
Cc: [email protected], [email protected], [email protected], "James Lal"
<[email protected]>, "Dylan Oliver" <[email protected]>, [email protected],
[email protected], [email protected], [email protected]
Sent: Tuesday, August 6, 2013 5:57:30 PM
Subject: Re: Proposal for addition of a new testing module
Hi Gareth,
I'm excited to see all the Marionette based JS support coming together!
I believe this fits better as a submodule within the larger Testing
Infrastructure module [1]. I think for the longevity of the project,
having it aligned with our larger testing infrastructure modules makes a
lot of sense.
I would also like to see a clearer definition of who should be the owner
and peers that you want to propose. There are essentially two ways
forward - an owner and a set of peers for all the repos or an owner and
a set of peers for each repo you are proposing. I think the first
method is easier for everyone, but it does depend on what your intention
is and what each person's expertise level is with those repos.
Here is a suggestion for the first method:
Marionette JS Tools (submodule of Testing Infrastructure)
Sub-Module Owner: James Lal <jlal> (is that right? should it be you?)
Peers:
- Gareth Aye <gaye>
- Ganesh Ghosh <gghosh>
- Jonathan Griffin <jgriffin>
- Michael Henretty <mhenretty>
- Ghislain "Aus" Lacroix <auswerk>
- James Lal <lightsofapollo>
- Mike Pennisi <jugglinmike>
- Evan Tseng <evanxd>
Does that approach make sense?
Thanks,
Clint
[1] https://wiki.mozilla.org/Modules/Core
On 8/6/2013 12:49 PM, Gareth Aye wrote:
Hello Governance!
tl;dr I want to propose adding a new module to maintain marionette js
tools.
Some of this looks much nicer when it's rendered as markdown, so I've
included a link[20] for those who'd prefer that.
A small group of gaia hackers have been hard at work over the past few
months in order to supply developers with end-to-end test tooling.
I've included a summary[1] of our work as well as documentation[2] for
test writers. Since I find it easier sometimes to read inlined
information in emails, I'll go ahead and mirror some of the high-level
from the summary here in my description of the components for which
the module would be responsible. Please forgive me for any duplication!
The module would be responsible for maintaining a number of small,
loosely coupled projects that have culminated in a product that helps
js hackers write end-to-end tests for things that run on gecko and
need to access privileged (ie chrome) and non-standard features. Our
tools leverage existing a-team work on the marionette server[3]. In
our work, we targeted Firefox OS developers (including webapp
developers), but there's no reason that other groups such as add-on
developers couldn't be consumers.
The related projects are (grouped by category):
### Test Harness ###
+ Marionette JS Runner[4]
+ Mocha JSON Proxy[5]
+ Mocha TBPL Reporter[6]
### Marionette Client ###
- JSON Wire Protocol[7]
- Marionette JS Client[8]
- Socket Retry Connect[9]
- Sockit To Me[10]
### Marionette Plugins ###
- Marionette Apps[11]
- Marionette JS Logger[12]
### Host Environment ###
- Marionette B2G Desktop Host[13]
- Marionette Firefox Host[14]
- Mozilla Download[15]
- Mozilla Runner[16]
### Profile Generation ###
- Marionette Profile Builder[17]
- Mozilla Profile Builder[18]
- Packaged Webapp[19]
I also feel compelled to recognize all of the wonderful people who
contributed (listed below in alphabetical order).
- Gareth Aye <gaye>
- Ganesh Ghosh <gghosh>
- Jonathan Griffin <jgriffin>
- Michael Henretty <mhenretty>
- Ghislain "Aus" Lacroix <auswerk>
- James Lal <lightsofapollo>
- Mike Pennisi <jugglinmike>
- Evan Tseng <evanxd>
James Lal deserves particular mention. He has been hacking on some of
these projects on and off for over a year now and has done an
incredible job architecting our tools, organizing related work, and
involving other contributors. Thanks James!
James and I would volunteer to be the initial module owners and would
invite auswerk, evanxd, and jugglinmike (each of whom have contributed
a significant amount of project code) to join us as module peers.
1.
https://developer.mozilla.org/en-US/docs/Marionette/Marionette_JavaScript_Tools
2.
https://github.com/mozilla-b2g/marionette-js-runner/blob/master/README.md
3. https://developer.mozilla.org/en-US/docs/Marionette/Marionette
4. https://github.com/mozilla-b2g/marionette-js-runner
5. https://github.com/mozilla-b2g/mocha-json-proxy
6. https://github.com/mozilla-b2g/mocha-tbpl-reporter
7. https://github.com/lightsofapollo/json-wire-protocol
8. https://github.com/mozilla-b2g/marionette-js-client
9. https://github.com/lightsofapollo/socket-retry-connect
10. https://github.com/mozilla-b2g/sockit-to-me
11. https://github.com/mozilla-b2g/marionette-apps
12. https://github.com/mozilla-b2g/marionette-js-logger
13. https://github.com/mozilla-b2g/marionette-b2gdesktop-host
14. https://github.com/mozilla-b2g/marionette-firefox-host
15. https://github.com/lightsofapollo/mozilla-download
16. https://github.com/lightsofapollo/mozilla-runner
17. https://github.com/mozilla-b2g/marionette-profile-builder
18. https://github.com/mozilla-b2g/mozilla-profile-builder
19. https://github.com/lightsofapollo/packaged-webapp
20.
https://gist.github.com/gaye/78e2bf50527587b8672d#file-proposal-for-addition-of-a-new-testing-module-md
_______________________________________________
governance mailing list
[email protected]
https://lists.mozilla.org/listinfo/governance
_______________________________________________
governance mailing list
[email protected]
https://lists.mozilla.org/listinfo/governance
