Media/WebRTC/2014-02-18

From MozillaWiki
< Media‎ | WebRTC
Jump to: navigation, search

1) Any hot platform issues that folks want/need to discuss or give a heads up on?

  • seccomp bugs/issues should get high priority if you need to help out on them.

2) App planning coming out of our work week in MV:

  • Minimum Landable Product bug tree:

https://bugzilla.mozilla.org/showdependencytree.cgi?id=972866&hide_resolved=1

  • User stories from RT:

https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AlJmiyFngeSwdFFpMjVCMm9QczdmZzJRNHJLekJzbFE&usp=sharing

  • Action Items:
    • St8, dmose, abr to review stories & check deps on MLP
    • Set up a Platform Selection meeting (tentatively tomorrow, Wed, at 9am PST)
      • ( Need to determine the testing/automated testing requirements for the app (start with initial, bare-bones testing needs and then build on that) - Nils will lead that with help from dmose, st8 and abr
    • Maire will figure out what pattern/regularity of team meetings makes sense given the new structure -- we'll discuss the possibilities and then Maire will decide and publish the decision (probably in dev-media)

3) Process

  • The team needs one process for interactions:
  • Devs will float between platform and apps work as needed
  • How an individual operates doesn't concern the team as long as team goals are met
  • Background info: https://wiki.mozilla.org/Talkilla/Agile_Process
  • Our goal is to ship code:
    • Design discussions up front with some estimation discussion as needed
    • code and iterate -- don't agonize too much about the estimate
    • All the design info and code patches should be in bugzilla
    • Try to break the work down into small pieces (roughly 2 weeks to implement or less) and then each piece gets a bug. Don't sweat it though if a few bugs can't be broken down into small pieces.
  • Dev practice and policies:
    • part of mozilla-central (which includes the github repo)
    • every patch needs a review, but we will commit to be fast about reviews (24 hrs or less during the work week)
    • Nightly will be our test bed -- so the app can change every day
    • Reviews: If we want to change the review policy (every patch committed to the master repo needs a review), we need to escalate this to Andreas.
  • Priorities
    • What are the big parts/first parts we need to focus on?
      • MLP
      • MVP

Deferred to follow up meeting

4) Platform Selection

  • Client
  • Social API / other rendering
  • Server
  • Development Platform (Node.js / Python with Pylons / etc)
  • Database Platform
  • What code lands where?
    • m-c, "twig", github (personal repos versus mozilla repo) etc
  • Testing frameworks
  • Client
  • Firefox
  • Other apps
Retrieved from "https://wiki.mozilla.org/index.php?title=Media/WebRTC/2014-02-18&oldid=938344"