WebCompat Summit (2015): Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(give my talk a more exciting title)
Line 72: Line 72:
| 1:50pm - 2:20pm || "Engaging with Web Developers for Site Outreach", by Colleen Williams (Microsoft)
| 1:50pm - 2:20pm || "Engaging with Web Developers for Site Outreach", by Colleen Williams (Microsoft)
|-
|-
| 2:30pm - 3:00pm || "MDN's Compatibility Projects", by Justin Crawford (Mozilla)
| 2:30pm - 3:00pm || "Web Compatibility Data: A Shared Resource", by Justin Crawford (Mozilla)
|-
|-
| 3:00pm - 3:15pm || Coffee & Snack Break
| 3:00pm - 3:15pm || Coffee & Snack Break

Revision as of 17:45, 3 February 2015

What is the Web Compatibility Summit?

Web Compatibility is an ongoing concern for browser vendors, spec writers, language designers, framework authors, web developers and users alike.

Our goal in organizing a WebCompat Summit is to bring together individuals representing these stakeholders in order to share ideas and problems and to coordinate compatibility, testing and standardization efforts.

We plan to hold three 90 minute sessions for individuals to present on topics related to compatibility.

If you would like to propose a 30 minute talk, or moderate a panel discussion for one of the sessions please fill out the form at http://goo.gl/forms/UtjFBkLVe7 (on page 2 of form).

Possible topics include, but are not limited to:

Standards & Web Compatibility

Discussion related to web standardization efforts and how they relate to web compatibility. E.g., specifying legacy features, implementing non-standard features, conformance test suites, etc.

Testing, Tooling & Web Compatibility

Discussion related to automated testing, measuring or crawling the web to understand the impact of removing support for certain web platform features, etc.

Outreach & Web Compatibility

Discussion related to doing "evangelism" or outreach work as it relates to web compatibility.

When and Where

Date

Wednesday, February 18th, 2015.

Start time: 9:30am

End time: 5:00pm

Location

Mozilla Mountain View

Mozilla Headquarters
331 E. Evelyn Ave.
Mountain View, CA 94041
  • Phone Number: +1 650 903 0800
  • Access Details: Please check in at reception on the first floor.
  • Map: https://goo.gl/maps/dy6SE

We have the Commons (110), Polaris (109) and Capella (108) rooms reserved.

RSVP

To help us with planning, please fill out the following Google form if you plan on attending or speaking on a topic: http://goo.gl/forms/UtjFBkLVe7.

Summit Schedule

Location: MTV Commons

Time Topic
9:30am Registration and Coffee
10:00am Welcome and Introductions
10:15am - 10:45am "Introduction to webcompat.com", by Mike Taylor (Mozilla)
10:55am - 11:25am "Beyond Vendor Prefixes", by Jacob Rossi (Microsoft)
11:30am - 1:00pm Lunch in the Mountain View office
1:10pm - 1:40pm "How CSS is being used in the wild", by Alex McPherson (QuickLeft)
1:50pm - 2:20pm "Engaging with Web Developers for Site Outreach", by Colleen Williams (Microsoft)
2:30pm - 3:00pm "Web Compatibility Data: A Shared Resource", by Justin Crawford (Mozilla)
3:00pm - 3:15pm Coffee & Snack Break
3:15pm - 4:45pm Unconference, lighting talks, or whatever else we feel like.
4:45pm - 5:00pm Closing Remarks


Location: Polaris or Capella

9:30 - 5:00pm Hack/work room available

Location: Polaris or Capella

9:30 - 5:00pm Unconference/breakout room available

Web Compatibility Issues

Here is a list of issues related to Web Compatibility. Feel free to add as potential topics of conversation.

Outreach

  • Sharing contact information without breaching the privacy of the contact.
  • Contact information will not necessary be valid for a long time. What about continuity? Proxy email addresses?

Web Standards and Regression

  • When a Web browser delivers a new feature which is breaking the Web
  • When a Web browser removes a feature which is breaking the Web
  • Measuring the Web for detecting legacy practices or current deployed issues
  • Understanding the locality of issues. Some issues are more acute in some regional markets.

User agent sniffing

  • Legacy detection scripts on the client side
  • Multiple JS all doing a kind of detection
  • Databases with old information about user agents.