The documentation of WebRTC is incomplete. Both reference and guide/tutorial content is either missing or incomplete. This epic involves completing that work; see the user stories within for details.

Some background on the work involved provided by @jwhitlock

How

Keep SVG as SVG, and add the titles at render time. You'd define a helper method like:

def include_svg(path, title=None):
    full_path = get_full_path(path)
    svg_raw = open(full_path).read()
    if title:
        parsed = parse_xml(svg_raw)
        title_elem = parsed.find('svg title')
        if not title_elem:
            svg_elem = parsed.find('svg')
            title_elem = svg_elem.add_child('title')
        title_elem.content = title
        svg_raw = parsed.serialize()
    return jinja2.Markup(svg_raw)

and then use it like:

<li class="footer-social">
    <a href="https://github.com/mdn/">
        {{ include_svg('includes/icons/social/github.svg', _('GitHub')) }}
    </a>
</li>

Examples of jinja2 helper methods:

https://github.com/mozilla/kuma/blob/master/kuma/wiki/templatetags/jinja_helpers.py

Advantages:

Python has a lot more power than Jinja2 macros, so you use SVGO to optimize the SVG as SVG, then modify it how you'd like. The SVG would be viewable as such, and could be used in other ways.

Disadvantages:

I'm not exactly sure how to implement those placeholder functions:

get_full_path - Django or Jinja2, probably undocumented code
parse_xml - libxml2 or pyquery

I'm also not sure exactly how to find and customize the XML. I'm pretty sure all this is possible, it would just take some digging to figure out how, plus tests.

Acceptance Criteria

• SVG titles are translated per locale
• Standard "Done" criteria for development tasks

As a WebExtension developer I want to know about the latest WebExtension features in Firefox 61, so that I can test and make use of new technologies.

As a web developer I want to know about the latest devtools features in Firefox 61, so that I can test and make use of new technologies.

As a Web developer I want to know about the latest JavaScript features in Firefox 61, so that I can test and make use of new technologies.

Acceptance criteria

• Write and/or complete the page RTCIceTransport
• Ensure each member of RTCIceTransport is documented completely
• Provide at least one example showing how RTCIceTransport is useful
• Document RTCIceRole
• Document RTCIceTransportState
• Document RTCIceGathererState
• Document RTCIceCandidatePair
• Document RTCIceParameters
• Document statechange event
• Document gatheringstatechange event
• Document selectedcandidatepairchange event
• Update BCD for RTCIceTransport
• Make sure the new types and events are in GroupData.json
• All of the types need to be added to BCD
• Add information related to these documents to overview materials as needed; explain ICE transports and their role in ICE transactions, etc.
• Ensure that https://developer.mozilla.org/en-US/docs/Web/API/WebRTC_API/Connectivity#Choosing_a_candidate_pair is complete
• Ensure all internal links are in place as needed, both in the new pages and in existing content that should link into the new pages

Create a branch of Kuma that runs under Django 1.9.

References:

• Upgrading Django to a newer version - advises updating to each version
• Release Notes, including notes for Django 1.9.
  • HTTP redirects no longer forced to absolute URL
  • Error views
• Django 1.9.13 is the last point release in the 1.9.x release cycle.
• bug 1401246 - Update to Django 1.11
• bug 1399639 - Upgrade Kuma dependencies

Acceptance Criteria:

• A branch is available that runs on Django 1.9, ready to be deployed, with passing unit tests (61 currently failing) and no deprecation warnings earlier than Django 2.0
• (Stretch) Deploy to stage for interactive testing

Tasks:

• Update dennis / click (@jwhitlock, r=@escattone) (PR 4775)
• Update django-babel (@escattone)
• Update redirect tests to test only path (backport to Django 1.8) (@jwhitlock)
• Remove protocol, hostname from redirects (just path)
• Fix instance creation order, other issues in spam and account tests
• Update DocumentJSONFeedGenerator to add content_type
• Rewrite error handlers to add exception parameter, return exceptions
• xfail tests that fail in 1.9, 1.10, but pass in 1.11

The goals are that a CDN in front of developer.mozilla.org will:

• improve response times since endpoints will mostly be served from a cached response and because the cached response will come from a server that is closer to the user
• greatly reduce the load on MDN, which will in turn reduce downtime events due to scrapers and other issues
• automatically provide a better level of protection against DDoS attacks (e.g., via AWS Shield)

See: This epic in Taiga

Move operations from being paid and supported by Marketing Engineering and Operations (MozMEAO) to Emerging Technologies (ET) by the end of October 2018.

References:

• MDN Operations Migration Plan

Acceptance Criteria:

• Agree on initial schedule
• Have initial meeting(s) with auditors
• Provide requested access and information

• Update 3rd-party packages to current versions, if possible
• Update to Django 1.11 in staging, production

References:

• Django Upgrade advice
• Kuma Package Updates Q1 2018
• bug 1401246 - Django 1.11 tracking bug

Acceptance criteria:

• Django 1.11 in staging and production without blocking bugs

See: This epic in Taiga for previous work

Acceptance criteria

• Document RTCTrackEvent
• Document each of RTCTrackEvent's members
• Document RTCTrackEventInit
• Document the track event following standard event layout
• Include information about why it fires (new track added to an RTCRtpReceiver)
• Include relevant links to other articles including WebRTC architecture, addTrack(), and so forth

Ensure that all of the ICE events are documented.

Tasks

Document each following events and their event handlers. If documents already exist, ensure they're up to date, accurate, and complete, with appropriate examples. In each case, ensure the corresponding event handler page is done as well.

RTCPeerConnection

• negotiationneeded
• signalingstatechange
• iceconnectionstatechange
• icegatheringstatechange
• icecandidate
• connectionstatechange
• BCD is up to date
• GroupData includes each of these

RTCIceTransport

• statechange
• gatheringstatechange
• selectedcandidatepairchange
• BCD is up to date
• GroupData includes each of these

Acceptance criteria

• All event pages exist and are complete
• All event handler pages exist and are complete
• All pages are linked from the appropriate places on the site, including the interface overview pages
• BCD is up to date

These need to be documented fully.

RTCIceCandidatePairStats

The main page and all subpages need to be written.

Specification: https://w3c.github.io/webrtc-stats/#dom-rtcicecandidatepairstats

RTCIceCandidateStats

The main page is about done but there are a number of subpages that need to be done still.

Specification: https://w3c.github.io/webrtc-stats/#dom-rtcicecandidatestats

• deleted
• networkType
• port
• priority
• transportId
• url

Acceptance criteria

• All missing pages have been created
• All new content has been submitted for review

Website performance has a massive influence on UX and SEO. We want to perform an audit of MDN focused on performance with the intent to learn about potential quick wins, big bets and the effort/impact involved.

See this epic in Taiga for previous work.

As a Web developer I want to know about the latest Media features in Firefox 61, so that I can test and make use of new technologies.

As a Web developer I want to know about the latest DOM features in Firefox 61, so that I can test and make use of new technologies.

1. • (Chris) Move a bunch of list properties from HTMLDocument to Document
2. • (Chris) Remove getUserData and setUserData support
3. • (Chris) Hide getPropertyCSSValue on Nightly
4. • (Chris) Return boolean from DOMTokenList's replace() method
5. • (Florian) Support SpeechSynthesis API in Android
6. • (sheppy) Update MutationObserver.observe() method
7. • (Florian) privacy.resistFingerprinting should disable WEBGL_debug_renderer_info
8. • (sheppy) PaymentRequest.show() should take an optional details update promise
9. • (sheppy) Treat document-level touch event listeners as passive. (Chrome scrolling intervention)
10. • (sheppy) Block ftp subresource requests inside http(s) pages
11. • (Florian) Get rid of DOMCursor
12. • (sheppy) [WebComponents] Implement :host pseudo class
13. • [Presentation WebAPI] enable Presentation API via preference instead of permission
14. • (sheppy) Implement Fetch API RequestDestination and Request.destination
15. • (sheppy) single-direction mousewheel should scroll horizontally when page's overall direction uses a vertical writing-mode
16. • (Florian) CSSStyleRule.selectorText setter is not implemented
17. • (Florian) Remove Element.createShadowRoot
18. • (sheppy) Make fetch() use "same-origin" credentials by default
19. • (Florian) Implement PerformanceServerTiming interface
20. • (sheppy) Remove createObjectURL()'s MediaStream overload
21. • Align various MediaList bits better with CSSOM spec draft
22. • (sheppy) Implement stricter data URL policy [this was previously updated in another bug]
23. • (sheppy) Prevent data: URLs from being used for XSS [same thing; previously updated in another bug]
24. • (sheppy) Get rid of File.lastModifiedDate
25. • (sheppy) Web Activities should only be started by a user interaction
26. • (Florian) Support IE extension Event.srcElement
27. • (sheppy) AudioBuffer ctor throws wrong exceptions with out-of-range arguments
28. • (sheppy) Disable WebVR for macOS in Release for FF60

User Story

As a product owner, I want a plan for putting interactive examples in Web API pages, so I know how much work is involved and roughly how long it may take.

Hi,

The doc at https://developer.mozilla.org/en-US/docs/Web/API/WebGL_API/Tutorial/Adding_2D_content_to_a_WebGL_context doesn't mention the dependency on glmatrix as an external script (except for one oblique reference to it in a comment that I saw after debugging extensively and googling about this).

As it stands, most folks will run into the issue of mat4 being undefined, which is confusing in particular because it's a type in the gl scripts. I added a script src to https://mdn.github.io/webgl-examples/tutorial/gl-matrix.js in order to resolve the dependency. I think the doc just needs to mention it more explicitly as a basic requirement for the tutorial.

Thanks,
Aaron

As a Web developer I want to know about the latest Layout features in Firefox 61, so that I can test and make use of new technologies.

jib points out that this page offers information about which stats each browser supports: https://webrtc-stats.callstats.io/verify

Acceptance criteria

• The page for RTCPeerConnection.getStats() is added
• BCD for getStats() is in place and has valid data for Firefox
• All RTCStats based dictionaries are documented
• RTCStatsReport page is complete and up to date
• Move content about dictionaries from RTCStatsReport page to their own pages; however, completing their documentation is covered under separate items in the WebRTC epic
• Complete documentation for the base RTCStats object; each member should have a subpage in place with complete content
• Verify BCD is in place for RTCStatsReport and RTCStats
• Submit to engineering for review

Acceptance criteria:

• Document the interface (write/update the overview page)
• Each property in the interface needs to be documented
• Include links to each of the individual track events

== Acceptance criteria

• Create page RTCIceCandidateStats
• Document all 10 properties

Establish a new Kubernetes cluster, billed to Emerging Technologies, with backing services like logging and alerts.

We're establishing the work share between MDN staff, MozMeao SREs, and Mozilla IT.

References:

• MDN Operations Migration Plan - April and May items.
• IT / MDN Weekly customer sync
• https://waffle.io/mozilla-itcloud/mdn-migration-project - IT project board
• Slack channel #mdn-migration

Acceptance Criteria:

• ET AWS account (ServiceNow RITM0061714)
• Kubernetes cluster available, low node resources for testing
• Servers monitored (currently New Relic, Datadog, with alerts going to Slack)
• Central logging, with long-term storage (currently fluentd, papertrail and S3)
• DNS for deployed servers (currently moz.works)

Tasks:

• Setup ET AWS account
• Give @escattone and @jwhitlock access to AWS account
• Deploy staging, production with New Relic credentials
• Move alerting to ET New Relic account
• Re-share charts on https://developer.mozilla.org/en-US/docs/MDN/Kuma/Server_charts
• Setup S3 buckets for papertrail archives - trying Elk first
• Setup moz.works replacement domain - seeing how far we get with allizom.org
• Establish papertrail account - trying Elk first
• Port log analyzer to Elk - tracked in https://github.com/mozilla-itcloud/mdn-migration-project/issues/18
• Port Worf to Elk - tracked in https://github.com/mozilla-itcloud/mdn-migration-project/issues/18
• Establish datadog account trying Prometheus first
• Create empty kubernetes cluster
• Setup fluentd app Prometheus (central logging)
• Setup datadog app (events to datadog)
• Setup #mdn-notices
• Setup #mdn-alerts
• Get access to SSO portal - Tracked in https://github.com/mozilla-itcloud/mdn-migration-project/issues/32

As a Web developer I want to know about the latest SVG features in Firefox 61, so that I can test and make use of new technologies.

Replace zamboni/amo localized URL infrastructure with one that is compatible with Django 1.11 and closer to Django's i18n toolkit

• References
  • Bug 1461350 - Re-implement locale-prefixed URLs
  • Task 4386 (Avoid using prefix in reverse()) of US 4053 (Stop using deprecated Django features).

Acceptance Criteria:

• All current unit tests pass
• Editing, login, logout, etc. still pass
• No change in current URLS (continue using en-US, zh-CN, etc.) or ?lang handling
• Locale-based redirects should still complete (but may change in number of redirects, or 301 vs 302)
• Compatible with Django 1.11

Tasks:

• Complete coverage of current middleware behaviour (@jwhitlock, mdn/kuma#4778)
• Update headless tests to run against development environment (@escattone, mdn/kuma#4779, mdn/kuma#4788)
• Improve is_valid path (@jwhitlock, mdn/kuma#4780)
• Make humans.txt a no-locale path (@jwhitlock, mdn/kuma#4786)
• Avoid runtime cache in tests (mdn/kuma#4789)
• Rewrite locale middleware as extension of Django LocaleMiddleware (@jwhitlock, r=@escattone, mdn/kuma#4790)
• Convert zone rebased URLs to temporary redirects (mdn/kuma#4792)
• Remove legacy locale tools (@jwhitlock, r=@escattone) (mdn/kuma#4793, mdn/kuma#4794)
• Expect current locale in URL in tests, code (@jwhitlock, r=@escattone)

• work with vendor to provide all necessary infos
• present options to team
• get in input
• select one to go forward with

Acceptance Criteria:

• KPI selected that will be used for future performance monitoring

• provide info to vendor about requirements
• document options
• get agreement on tool choice from team
• get contract and budget in place to set up monitoring
• implement custom KPI monitoring
• set up speedcurve

Acceptance Criteria

• Continuous monitoring in place for chosen KPI

With the move of the MDN dev team out of marketing, we don’t have access to the marketing SREs anymore and need to find a way to solve those problems in some other way.

Acceptance criteria

• Staging and Production are migrated to IT-managed Kubernetes clusters
• Daily operations moves from MozMEAO SREs to IT and MDN staff
• MDN resources in MozMEAO are decommissioned

References

• IT / MDN Weekly customer sync
• https://github.com/orgs/nubisproject/projects/4 - IT project board
• https://waffle.io/mozilla-itcloud/mdn-migration-project - New IT project board
• https://github.com/mdn/infra/projects/1 - New IT project board
• MDN Migration Project milestones
• Slack channel #mdn-migration

#User Story#
As a web developer, I want helpful interactive HTML element examples, so I can quickly see how an element works

See: This epic on Taiga

Work on more compat data migration from old static wiki tables to JSON data stored in the https://github.com/mdn/browser-compat-data repository.

Acceptance criteria:
80% of data migrated, i.e. 500 more pages use the new table.