Skip to content

Latest commit

 

History

History
194 lines (147 loc) · 8.43 KB

README.md

File metadata and controls

194 lines (147 loc) · 8.43 KB

Responsive images meetup

##Location and time Date: Tuesday, 10th September, 2013. Time: 10am-6pm

Location:

16Bis Boulevard Montmartre
75009 Paris, France

(note: you want the 16 *Biz* entrance - not the 16... look for Mozilla on digital panel!)
<iframe width="425" height="350" frameborder="0" scrolling="no" marginheight="0" marginwidth="0" src="https://www.google.com/maps?sll=48.873288000000045,2.32527799999999&sspn=0.010838193662898222,0.0219711170879061&t=m&q=16+Bis+Boulevard+Montmartre+75009+Paris,++France&dg=opt&ie=UTF8&hq=&hnear=16+Boulevard+Montmartre,+75009+Paris,+%C3%8Ele-de-France,+France&z=14&iwloc=A&ll=48.871838,2.341121&output=embed"></iframe>
View Map

About

The purpose of the meetup is to discuss the proposed solutions (see below), assess the obstacles to their implementations, and build momentum behind the problem space. A little more detail:

For the last couple of years, various folks have been working towards finding a way to bring responsive images to the Web, with significant interest from Web developers. Although we now have 3 proposals on the table ( srcset, picture element and client hints), we've had trouble getting sufficient momentum behind browser implementations that would let the market decide which solutions fulfills the use cases most effectively.

In the mean time, developers are makig due with custom pollyfills that often prevent browsers from loading the image resources until after the DOM was (at least partially) loaded and Javascript has run. This directly hinders the performance work browser engineers have done over the years to optimize resource loading, and get requests on the wire as soon as possible ( according to their priority). That leaves developers with the dilemma: "Do we stall the image load?, or download unnecessary image data which will slow down the overall load time and inflate the user's bills?"

Proposed agenda

  1. Welcome and tweak agenda
  2. Developer's perspectives
  1. Introduction to each of the proposed solutions:
  1. Implementors feedback on the solutions for each of the use-cases
  1. Overlap among solutions
  2. Related specs
  1. Next steps

Lunch @ ~12:30 - provided by Mozilla. Resume at 1:30pm.

We will go out for dinner/drinks afterwards to Le Zinc des Cavistes. If you want to joing us, please let us know!

IRC Server details

Using your browser: http://irc.w3.org (channel: #respimg)

Using a client that supports URLs: irc://irc.w3.org:6665/#respimg

Otherwise: Server: irc.w3.org Port: 6665 Channel: respimg

Proposed solutions

Who is attending?

Representatives for the following companies and organizations have registered:

  • Adobe
  • Akamai
  • Apple
  • BBC
  • Drupal
  • Ekino
  • Google
  • GPAC
  • Microsoft
  • Mozilla
  • W3C
  • Opera
  • PMLA
  • Shoogle designs
  • WOPE-framework

The event is on Lanyrd if you'd like to make your attendance more public.

Please note that you cannot register through the Lanyrd page. If you'd like to register for either remote or in person attendance, please contact the organizers listed below)

Remote participation

Note the meeting starts at 10AM Paris time. See the meeting planner for a time near you.

** Please sign up to participate remotely - we will email you a link on the day **

To participate, you will need to install the Vidyo client to access the video stream (similar to what you have to do with G+ hangouts). The Vidyo client is available in the Apple App store, in the Google Play Store and also for Mac OX, Windows and Linux platforms.

  • IRC - please join us IRC for backchat and minutes - irc://irc.w3.org:6665/#respimg

Organizers contact info

Getting to town

Bus from Charles de Gaulle

From Paris-Charles de Gaulle Airport (CDG) you can take the RoissyBus for 10 Euros to get downtown, about a ten minute walk from the office. It departs from Terminals 1 and 2; buy your tickets just before the doors outside. The bus is non-stop from CDG to downtown and stops near Palais Garnier. From there you can walk to the office or many hotels nearby.

Metro from Gare du Nord

If you come into Paris at the Gare du Nord you can take:

  • Metro line #4 (pink line) in the direction of Porte d'Orleans, change after two stops at Strasbourg St Denis.

  • then Metro line #8 (purple line) in the direction of Balard to Grands Boulevards.

The Grands Boulevard Metro is on the same road as the Office. You can buy a Metro ticket from automated machines at all metro stops. You just need a regular Billet. The price is 1.70Eur and is valid in all directions for one Journey. This journey takes about 10 - 15 mins start to finish. You can pick up a map of Paris on the Eurostar itself.

Taxis G7

Book by phone:

  • +33 1 47 39 00 11 (to book in French)
  • +33 1 47 39 82 28 (for an English speaking Agent)

Book by internet: https://www.taxisg7.com/abonne/commande-taxis

Wifi for guests

The Paris offices have a wifi network dedicated for guests. The SSID is "Mozilla Guest" and we wil give you the password on arrival.

Accomodation

Hotels

Hotel Tryp Francois. Across the street from the Mozilla office. If you ask for a quiet room, it is a good hotel. Rooms clean. Internet included (from LAN cable, no WiFi).

Holiday Inn - Paris Opera - Grands Blvds

Hotel Mercure Opera Cusset. Internet is not included. About 5 mins walking to office via the main street.

Hotel Bergere Opera nice hotel, small rooms but not bad.

Hotel Acadia Opera

Radisson Blu Ambassador 5 minutes walk. Very nice.

Hotel Corona Opera Nice enough hotel; really close to the office. Staff are nice and helpful and the rooms are nice, but the internet can be bad.