Auto-tools/Projects/Mozbase/Automation-Refactor/Meetings/2013-06-18: Difference between revisions

 
(3 intermediate revisions by the same user not shown)
Line 21: Line 21:
=== Issues of the Two Weeks (since you looked at me) ===
=== Issues of the Two Weeks (since you looked at me) ===
* Agenda for mozbase work week? Propose items below
* Agenda for mozbase work week? Propose items below
** brainstorm the creation of a mozbase "manifesto" -- both a high-level statement vision of the purpose of the project, and a detailed roadmap of how to make it live up to that vision [jhammel: a big +1]
** brainstorm the creation of a mozbase "manifesto" -- both a high-level statement vision of the purpose of the project, and a detailed roadmap of how to make it live up to that vision [jhammel: a big +1][nalexander: another big +1 here]
[nalexander: another big +1 here]
*** what components are we missing, if any?
*** what components are we missing, if any?
*** where should shared code live that doesn't belong in a mozbase component?
*** where should shared code live that doesn't belong in a mozbase component?
Line 36: Line 35:
*** moztest? common code etc.
*** moztest? common code etc.
** manifestdestiny/mozprocess lots of work to do (tracking bugs?)
** manifestdestiny/mozprocess lots of work to do (tracking bugs?)
== Decisions for /the future/ ==
 
1. CI failures: to note on bug?
==== Decisions for /the future/ ====
-- add to policy :)
* CI failures: to note on bug?
2. mock, etc, libraries in testing?
** add to policy :)
* mock, etc, libraries in testing?
** leaning towards not using external dependencies unless absolutely necessary
 
==== Mozbase, Packaging, Mirroring and the Future of M-C ====
==== Mozbase, Packaging, Mirroring and the Future of M-C ====
==== Areas of Development ====
==== Areas of Development ====
Confirmed users
656

edits