WeeklyUpdates/2008-12-15: Difference between revisions

Added user stories
m (→‎QA: spelling nits)
(Added user stories)
Line 19: Line 19:
Please send FotT nominations to [mailto:asa@mozilla.org asa@mozilla.org]. This is a great opportunity for the community to recognize those who go above and beyond, so please tell me when you see that happening. Thanks.
Please send FotT nominations to [mailto:asa@mozilla.org asa@mozilla.org]. This is a great opportunity for the community to recognize those who go above and beyond, so please tell me when you see that happening. Thanks.


= Development Updates =
= User Stories =
== Use case: install ==


== Branch work: Firefox 2.0.0.19 / 3.0.5 / Major Update ==
'''As a user, I can tap install on a marketplace page and an APK is downloaded to my device so that my phone's native package installer can install the app.'''
* '''Firefox [[Releases/Firefox_2.0.0.19|2.0.0.19]] / [[Releases/Firefox_3.0.5|3.0.5]]'''
** On track for release tomorrow
** Last planned Firefox 2 release
** Phishing Protection is off in Firefox 2.0.0.19
** Changed messaging all around to note this
* '''[[Releases/Thunderbird_2.0.0.19|Thunderbird 2.0.0.19]]'''
** Schedule on the wiki
** Currently planning release for early January
** Beta release later this week
* '''[[Releases/Firefox_3.0.6|Firefox 3.0.6]]'''
** Scheduling release for early February
** Code freeze date is January 6
* '''[[Releases/Firefox 2.0.0.19 MU | Firefox 2.0.0.19 -> 3.0.5 Major Update]]'''
** Currently scheduled for early January after Thunderbird 2.0.0.19
** Will be dependent on localization of the new major update text


== Gecko 1.9.1 ==
We will be modifying the implementation of the mozApps.install() and
* It's all Beta 3, yo. Planned code freeze is Jan 13.
mozApps.installPackage() APIs on Android. On webapp install, Fennec
* For weekly engineering meeting notes and other info see the [https://wiki.mozilla.org/Platform Platform page].
will download an APK which is generated from the manifest URL which
* [http://wiki.mozilla.org/Platform/1.9.1 Interesting queries related to Gecko 1.9.1]
is  passed to the apk-builder.
* [http://tinyurl.com/3jsumu 155 1.9.1 blockers].
** [http://tinyurl.com/4ombdf 28 Blocking 1.9.1 P1s]
** [http://tinyurl.com/4lt8ah 50 Blocking 1.9.1 P2s]
** [http://tinyurl.com/5x59y5 26 Blocking 1.9.1 P3s]
** [http://tinyurl.com/47df5d 51 Blocking 1.9.1 w/ no priority.]


== Firefox 3.1 ==
In this manner, we are able to avoid changing any marketplace code,
'''[[Releases/Firefox_3.1b3|Firefox 3.1 Beta 3]]'''
and support third-party webapp marketplaces.[at the very least, with
* proposed schedule as follows:
this method we avoid the marketplace trying to detect whether the
** Dec 31 - string freeze
phone is android or not -BillW]
** Jan 13 - code freeze
** Jan 19 - QA start
** Jan 26 - ship to users
** will re-evaluate in early January, hope to be able to accelerate
** if you have counter proposals or problems, please come to tomorrow's [[Platform#Meeting_Notes|development meeting]].


* '''note:''' string freeze is end of 2008
* workin' on Beta 3 ([http://people.mozilla.org/~beltzner/triage.html triage queries])
** [http://tinyurl.com/5n2gdg Firefox 3.1 Nominations]
** [http://tinyurl.com/5vuco5 Firefox 3.1 Blockers]
** [http://tinyurl.com/5uc5nk Firefox 3.1 Blockers that need 1.9.1 landing]
** [http://tinyurl.com/5d5qwm Firefox 3.1 - easy polish bugs we're looking to take]
** [http://tinyurl.com/6delb6 Firefox 3.1 - hard polish bugs we're looking to take]


== TB 3 ==
=== Implementation of the apk-builder ===
* Thunderbird 3.0 beta 1 has [http://ascher.ca/blog/2008/12/09/thunderbird-3-beta-1-a-platform-for-innovation-shapes-up/ shipped]
* Beta 2 work and planning is underway


== Mobile ==
It is intended that apk-builder use Android's standard toolchain.


* Planning A2 release this week
The apk-builder accepts a URL to a JSON document, that could be a
* [https://wiki.mozilla.org/Mobile/Notes/15-Dec-2008 Weekly update]
webapp  manifest or mini-manifest. It should detect the difference
* Kicked off [http://www.christiansejersen.com/blog/2008/12/10/fennec-mobile-firefox-for-symbian/ Symbian port] for Fennec, you can follow progress [https://wiki.mozilla.org/Mobile/Symbian here]
between a  packaged app and hosted app and act accordingly.


== IT ==
The apk-builder constructs an Android project from a template and
* Wrapped up Zeus ZXTM AMO performance tests
data  in the webapp manifest, including icons, string translations,
** a couple lingering log issues
permissions, and web activities.
* Upgraded bouncer/download.mozilla.org database server


== Release Engineering ==
Both webapps and Android have very similar concepts. There is some
* [http://oduinn.com/2008/12/15/nokias-nokias-everywhere/ Aki's work on mobile and talos]
impedance mismatch, though this is not particularly relevant for the
* Enabling a11y tests last week were backed out; we *think* we've got it; will try again this week.
scope of this project.
* Backup your machine! (Thanks to Justin and Sean for their help!)


== QA ==
The exception to this is around [https://developer.android.com/tools/publishing/app-signing.html APK signing].
Android apps are expected to be signed by the developer, regardless of whether they
seek any special permissions. The same signature is used to  sign
successive versions of the same APK, otherwise the update will not
be allowed to continue.


QA had a great Work On-Site week last week!
For packaged webapps, the package.zip and mini-manifest files will be included in the APK.


'''Web Dev testing, Metrics, Accessibility, Localization'''
Once the apk-builder has created an Android project, it can build it
with ant, javac and the rest of the Android toolchain.


* WebDev testing:
By design, the Android project's template contains no Java code. All code
** SUMO- Verified [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Other&product=support.mozilla.com&target_milestone=0.8&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=VERIFIED&resolution=FIXED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-12-07&chfieldto=2008-12-14&chfield=bug_status&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&known_name=sumo0.8fixed&query_based_on=sumo0.8fixed&field0-0-0=bug_status&type0-0-0=changedby&value0-0-0=stephen.donner%40gmail.com 9 bugs] for the 0.8 milestone. Continued testing search for [https://wiki.mozilla.org/Support/SUMOdev_Meeting_Notepad#Next_release 0.8]
is contained in a [https://developer.android.com/tools/projects/index.html#LibraryProjects library-project].
** Community Store, v2.0 - Tested and [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Other&product=Websites&component=communitystore.mozilla.org&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=VERIFIED&resolution=FIXED&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-12-07&chfieldto=2008-12-14&chfield=bug_status&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=bug_status&type0-0-0=changedby&value0-0-0=stephen.donner%40gmail.com verified the 9 fixes] thus far
Both, especially the library project, are being actively developed
**Funnelcake 04-  [https://bugzilla.mozilla.org/show_bug.cgi?id=468179 Tested and shipped on Sunday night]
in  parallel to the apk-builder.
** Tested QMO2
** IT - Spent some time testing AMO in production with the [https://bugzilla.mozilla.org/show_bug.cgi?id=467502 Zeus load-balancer]
** Mozilla.com - Verified [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Other&product=Websites&component=www.mozilla.com&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=VERIFIED&resolution=FIXED&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-12-07&chfieldto=2008-12-14&chfield=bug_status&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=bug_status&type0-0-0=changedby&value0-0-0=stephen.donner%40gmail.com&field0-1-0=short_desc&type0-1-0=notsubstring&value0-1-0=redesign 6 Mozilla.com bugs]
* Accessibility:
** Created patch to properly expose search textboxes in the 3.1 a11y code. See {{bug|469367}}.
** Investigating accessibility framework support in [https://addons.mozilla.org/en-US/firefox/addon/9018 MozMill].
** Working on a mochitest file for {{bug|469367}} to test the accessibility attributes generated by the ARIA markup newly introduced in the search textbox's XBL widget.
* Metrics
** ~5% percent of the files in the source tree have 10 or more bug fixes. max number of bug fixes in a file is 69 since the m-c tree opened.  Some of these have zero or low coverage
** Worked with rsayre to do an updated coverage run with all the mochitest, chrome, browser, reftest, xpcshell, and bc's JS tests.  The results will include details down to line coverage.  The run will be against m-c trunk.
** Focusing a small project on the JS engine files.  There are 50 main files but only 8 are very active.  bc, mnandigama, together with the JS team, will be looking at how to boost the coverage of some of the active files:
  FILENAME        FULLPATH             CODECOV% BUGSFIXED
  jstracer.cpp    /js/src/jstracer.cpp  75.4 46
  jsobj.cpp      /js/src/jsobj.cpp          64.7 21
  jsapi.cpp      /js/src/jsapi.cpp          55.1 16
  jsinterp.cpp    /js/src/jsinterp.cpp  71.4 15
  jscntxt.h      /js/src/jscntxt.h          100 14
  jsparse.cpp    /js/src/jsparse.cpp  62.5 10
  jsarray.cpp    /js/src/jsarray.cpp  70.2 10
  jsopcode.cpp    /js/src/jsopcode.cpp  41.1 10


'''Test Development'''
It is desirable that the project template and library code be taken
* General
live from a code repository so that changes are easy to incorporate
** Attempted to land A11y tests again
in to the workflow.
** Filed several [http://tinyurl.com/5e6qvd crash bugs].
** Created the [https://wiki.mozilla.org/Releases/Firefox_3.0.5/RRRT RRRT Pages for Firefox 3.0.5]
** Worked on reducing crashes, SVG in CSS (SVG clip path etc), CSS Border Radius, and Audio/Video tests
** Improved automation of code coverage scripts, removing manual steps
** Started a "QAC Redesign" Effort with a great team of Brian King, Zach Lipton, and Heather Arthur.  The first [https://wiki.mozilla.org/User:Ctalbert/QAC_Discussion meeting notes] are available.
* Mozmill
** New Mozmill point release due out this week - you'll need to re-download from AMO, no update service
** Continued Progress toward 1.0 at the end of the month
* Fennec
** Created a Log Viewer for [http://people.mozilla.com/~jmaher/mochitest.htm Fennec Test Results]
** Investigated many of the Mochitest failures on Fennec, and found that most are due to the fact that SynthesizeKey does not work without focus -> {{Bug|455891}} and {{bug|465216}}
* JS/Sisyphus/Leaks
** Improved automation on Sisyphus and Memory Leak testing
** Worked on the JS Reftest framework, should land this week
** About to start the 1,000,000 top site test, looking for JS regressions and memory leaks.


'''Test Execution'''
== Use case: update ==
* General
** The new [http://quality.mozilla.org QMO] coming this week!
** Triaged about 40 QMO2 bugs
** [https://wiki.mozilla.org/QA/TDAI/Inventory:notes Litmus redesign] session last week. (working with TestDev)


* Project Status
'''As a user, I can have my phone check for updates and have my phone download them so that I may keep my webapps safely up-to-date.'''
** Shipped [https://wiki.mozilla.org/Releases/Firefox_3.1b2 Fx3.1b2] to world last monday (12/8)
** Shipped Fx3.0.4 & [https://wiki.mozilla.org/Releases/Firefox_2.0.0.19 Fx2.0.0.19] to beta last wednesday (12/10)
** Plans to ship [https://wiki.mozilla.org/Releases/Firefox_3.0.5 Fx3.0.5] & [https://wiki.mozilla.org/Releases/Firefox_2.0.0.19 Fx2.0.0.19] to world this tuesday (12/16)
** Plans to ship [https://wiki.mozilla.org/Releases/Thunderbird_2.0.0.19 Tb2.0.0.19] to beta this thursday (12/18)
** Fx3.1 feature tracking [http://spreadsheets.google.com/ccc?key=pnyCb4cp33faqpi709iEhcA&hl=en spreadsheet]
*** Testplan completion: 89%
*** Testcase completion: 73%
*** Feature status
**** HTML 5 Drag and Drop, 100%, 2 (litmus), 100%, N/A (554 cases already done by
**** Media Queries, 100%, 202 (reftests), 100%, N/
**** Element Traversal, 100%, 60 (mochitest), 100%, N/A (finished and turned on 142 from
**** Script Defer, 100%, 0, 100%, N/A (dev had created 2 tests already)
**** Blocklist /Software Updates Testing, 100%


== Security ==
The synthesized APK is relatively lightweight. For hosted apps,
Gecko  can manage updating appcache and resources generated at
runtime.  Updating anything used to build the APK should trigger a
rebuild of the APK itself. In practice, this means the APK should be
rebuilt anytime  the webapp manifest changes. From a computation
point of view, the  detection of change in the manifest and the
rebuilding of the APK would  be sensibly done on the server.


* Participated in the W3C "Security for Access to Device APIs from the Web" workshop
For packaged apps, any change of the app should trigger a rebuild,
however, we are working with the assumption that a release of the
app is  needed, and a change in the mini-manifest will be triggered.


== Marketing/PR ==
Android apps have a hard requirement that the versionCode, a non
user facing integer representation of the version string, be
positively increasing.


'''PR'''
The same android signing key should be used to sign the updated APK
* eWeek [http://www.eweek.com/c/a/IT-Infrastructure/Top-10-News-Stories-of-the-Year/ Top 10 News Stories of the Year]
as was used to sign the previous version of the APK.
* Firefox 3.1 Beta 2 covered in [http://arstechnica.com/news.ars/post/20081208-first-look-firefox-3-1-beta-2-now-with-private-browsing.html Ars Technica], [http://computerworld.com/action/article.do?command=viewArticleBasic&articleId=9123098&intsrc=hm_ts_head ComputerWorld], [http://www.informationweek.com/news/internet/browsers/showArticle.jhtml?articleID=212300270&subSection=News InformationWeek], [http://www.technewsworld.com/story/Mozilla-Boosts-Stealth-Speed-in-New-Firefox-Beta-65433.html?wlc=1229370646 TechNewsWorld] and [http://blog.wired.com/business/2008/12/firefox-31-beta.html WIRED]
* Mozilla and Racepoint Group UK won Best Technology and Consumer Electronics PR Campaign for Mozilla Firefox 3 launch at the [http://www.excellence-awards.eu/ European Excellence Awards 2008]
* Firefox add-on featured in [http://www.readwriteweb.com/archives/a_firefox_add-on_for_app_addic.php ReadWriteWeb]
* Firefox wins ReadWriteWeb [http://www.readwriteweb.com/archives/top_10_consumer_apps_2008.php Top 10 Consumer Web Apps of 2008]
* Firefox included in BusinessWeek's [http://images.businessweek.com/ss/08/12/1210_best_worst_tech/10.htm Best Tech Products of 2008]


'''Events'''
* Last weekend, the second European Mozilla Add-ons Workshop took place in Madrid. 50 people attended the event. Paul Rouget gave a presentation about how to create an Add-on for Tuenti, the biggest Spanish social network. Hopefully, people from Spain will take ownership of the project and drive it forward.
* Add-on-Con: Collecting [https://wiki.mozilla.org/Add-on_con#Add-on-Con_Feedback feedback].


'''Quarterly Survey'''
== Use case: developer's own keys ==
* Quarterly Survey will be released tomorrow in ten locales.
* Attached to the 3.0.5 "What's new page" and its our first time hosting the survey on surveygizmo.com.
* Thanks to Pascal/Sam/Stephen Donner/Wil for all their hard work.


'''As a developer, I can use my own key to sign my Android APK, so I can use the key elsewhere.'''


'''Impact Mozilla'''
Changing keys for an already published APK is impossible.
* Voting site is now live!
* Please take some time to carefully consider all ten finalists before [http://impactmozilla.com/vote/ casting your vote]
* Voting closes Wednesday at Noon pacific time


== Support ==
For a large proportion of developers, a randomly generated APK
* Chris and David have been reaching out to European localizers to get a better understanding about what's working well and what needs improvement on SUMO. Based on the gathered feedback, the two top issues are:
signing key will be sufficient.
** Site performance -- site is still too slow
** Localization priorities are unclear -- hard to know what to work on first, and the status of the localization
** [https://wiki.mozilla.org/Support/l10n:Feedback Complete feedback]
* SUMO 0.8 to be released on Thursday
** New search engine
** CSAT for Live Chat
** Chris will blog about the release this week


== Metrics ==
However, a few will want to be able to use their own. During app
* Funnelcake
submission, if the app is to be on Android, they should have the
** Funnelcake shipped last night and will run for a 24-hour period today
opportunity to upload their own key.
** Thanks to Kev and the build, QA, web dev and IT teams for making this happen
** We still owe everyone a blog of metrics post regarding the findings from last month's funnelcake


== Evangelism ==
== Use case: pre-submission development ==


* Asa is evaluating and documenting Theora streaming options for Air Mozilla, launch day activities, and general video streaming going forward. Asa will also be assisting with two Air Mozilla streamed events this week, (Mitchell on Tuesday and Li Gong on Wednesday) and working with Mozilla Online to get some of the Firefox Flicks videos updated and translated for use in the Mozilla China market.
'''As a developer I would like to be able to test my APK without submitting it to the marketplace.'''
* Firefox 3.1 documentation work continues; the last major known area of documentation to be tackled is now underway: offline resources.  There's still plenty of other stuff to do, but the individual documentation items are generally smaller bites.
* Demos page: https://wiki.mozilla.org/Firefox3.1/Demos - please help by adding!


== Labs ==
It is assumed that the Android toolchain is rather cumbersome and
*Labs Night this week - Thursday 12/18, 6pm-9pm in Bldg K. Join us for updates on Labs projects, open discussion, and pizza. RSVP [http://upcoming.yahoo.com/event/1436111/?ps=5 here].
not  interesting enough for the webapp developer to actually set it
up  successfully.


== Webdev, Add-ons, AMO ==
The apk-builder should accept a POST of the webapp manifest and
resources needed for the webapp, and return an APK. A command line
or  option in the app manager will be used to send the POST.


'''AMO'''
The APK should not be publishable on an APK app-store, e.g. signed
* [http://osunick.com/ Nick Nguyen] and [http://blog.fligtar.com/ Justin Scott] have joined the Add-ons team.  Nick will be leading the Add-ons product, and Justin will be continuing his work with IT, webdev and marketing to release new and exciting add-ons projects.
with a [https://developer.android.com/tools/publishing/app-signing.html#debugmode debug key],
* Add-on Con was a huge success -- thanks to Mary Colvig for putting this together, and thank you to everyone who helped with booth duty!
icon marked with "IN TEST".
* [http://tinyurl.com/AMO-404-fixed AMO 4.0.4] was pushed on Thursday, Dec 11 -- special thanks to Frederic Wenzel, who fixed 20 bugs in this release
* AMO 4.0.5 [http://tinyurl.com/69hply open bugs] & [http://tinyurl.com/62dhds fixed bugs] - '''Freeze - Dec 22'''
* Unfortunately, AMO logs were affected by a change in load balancing hardware in {{bug|467502}} -- add-ons statistics were affected and IT is working to resolve the issue


'''Socorro (crash reporting)'''
This use of the apk-builder should be invoked by the developer from
* Socorro repartitioning is bocked by replication {{bug|469220}} and {{bug|469215}} -- Lars' work there is done and ready to roll out, but we want to make sure we have proper backups before we repartition, because a failed migration would be catastrophic and require a complete restore.
the command line or App Manager.
* Austin King has been blazing away on [https://bugzilla.mozilla.org/show_bug.cgi?id=411424 mean time between failure (MTBF)] and [https://bugzilla.mozilla.org/show_bug.cgi?id=411358 URL reports], and we hope to roll these out this week.
* Neil has been working on hi-fidelity mocks based on his [http://blog.mozilla.com/webdev/2008/12/04/socorro-wireframes/ Socorro wireframes] from last week


'''SUMO (Mozilla Support)'''
In coming releases, we would like the developer to be able to
* In the final throes of [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Other&product=support.mozilla.com&component=Chat&component=Forum&component=General&component=Knowledge+Base+Articles&component=Knowledge+Base+Software&component=Localization&target_milestone=0.8&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&;emailreporter2=1&emailqa_contact2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit SUMO 0.8], to be released Thursday night
construct an APK without calling out to a server, either from the
* [http://bugs.locamotion.org/show_bug.cgi?id=626 tiki2po] landed in the [http://translate.sourceforge.net/wiki/toolkit/index translate toolkit]; will enable SUMO L10n in Verbatim
command line or App Manager.


'''Webdev Projects'''
== Use case: post-submission review ==
* If you haven't checked out the [http://communitystore.mozilla.org/ community store], you should! :)
* [http://feeds.stage.mozilla.com/ The Lizard Feeder] is staged, and Les is working on its beta launch this week.
* Django was merged onto the Pootle trunk last week!
* Mmmmm.... Funnelcake....


== L10n ==
* '''As a reviewer I can run the APK on my Android phone. '''
* Moving 5 languages out of beta for Firefox 3.0.5
* '''As a developer I can run the same APK as the reviewer.'''
** bn-IN, Bengali
 
** eo, Esperanto
The APK should not be publishable on an APK app-store, e.g. signed
** gl, Galician
with a [https://developer.android.com/tools/publishing/app-signing.html#debugmode debug key],
** hi-IN, Hindi
icon marked with "IN REVIEW".
** lv, Latvian
 
*  Launched the L10n Testing Survey.  If you are a localizer, [http://surveys.mozilla.org/?id=18 please take it].
== Use case: post-review acceptance ==
*  Pascalc has lead the 2.0.0.19 --> 3.0.5 update
 
* Silme brownbag with Adrian Kalla this Thursday, December 18.  Please contact [mailto:akalla@mozilla.com Adrian Kalla] if you have any questions.
'''As a developer, I can download the APK that will be installed on user's devices, so I can distribute it myself.'''
 
Once the webapp is ready for publishing, the developer should
receive (as part of an existing email?), a link to the APK.
 
= Reference =
 
* [https://github.com/jhugman/synth-apks Code for working prototype]
* [https://docs.google.com/a/mozilla.com/presentation/d/1fzlE7ARpgtw17U1qsIZxqpUcS2DNniFOCJWzF2Id5Mw/edit#slide=id.p18 Slides from air.mo presentation Oct 28]


= Foundation Updates =
= Foundation Updates =
14

edits