The XMPP Standards Foundation will hold its fifth “XMPP Summit” meeting on July 21 and 22, 2008, in Portland, Oregon, USA (the same week as OSCON 2008). Read on for details.
Participation is open to all developers, service operators, and other interested individuals. Please note that this is a hard-code technical get-together with plenty of coding sprints, hackfests, interop testing, brainstorming sessions, geeky lightning talks, etc. This meeting is not intended for marketing presentations and other fluff!
If you would like to participate, please join the firstname.lastname@example.org mailing list and introduce yourself.
The following individuals have indicated that they will attend:
- Dietrich Ayala, Mozilla
- Nathan Bell, Intrigo
- Eric Butler
- Fadi Chalfoun, Intrigo
- Diana Cionoiu, Yate
- Anders Conbere
- Blaine Cook
- Leah Culver, Pownce
- Kevin Davie, Zleek
- Gaston Dombiak, Jive Software
- Seth Fitzsimmons, Yahoo
- Nathan Fritz, Seesmic
- Will Glozer, Heysan
- Jared Hanson
- Artur Hefczyc, Tigase Project
- Evan Henshaw-Plath
- Christian Hergert, MySpace
- Joe Hildebrand, Jabber Inc.
- Ron Hose, TokBox
- Justin Karneges, Psi project
- Sam Keen, Portland PHP Users Group
- Asheesh Laroia, Creative Commons
- Patrick Logan
- Eric Marcoullier, Gnip
- Chris Messina, Vidoop
- Ralph Meijer, Mediamatic
- Jack Moffit, Chesspark
- Pushpendra Mohta, Vayusphere
- Allen Morris
- Dan Mosedal, Mozilla
- Don Park
- Russell Okamoto
- Michael Ossareh, Heysan
- Darian Anthony Patrick, University of Pennsylvania
- Adam Pisoni, Geni
- Evan Prodromou, Identi.ca
- Mickaël Rémond, Process-One
- Peter Saint-Andre, XSF
- Krishna Sankar, Cisco
- Jérôme Sautret, Process-One
- Sean Smith
- Brendan Taylor
- Mike Taylor, Seesmic
- Matt Tucker, Jive Software
- Justin Uberti, Google
- Jud Valeski, Gnip
- Ezra Zygmuntowicz, EngineYard
As posted by Peter Saint-Andre on the email@example.com list, 2008-07-16 (with further tweaking).
This is a rough agenda. As always, agenda bashing is welcome. As much as possible, I’d like to keep the spirit of an unconference.
The summit hours will be something like this:
- Monday 9:30 AM to 4:30 PM
- Tuesday 9:30 AM to 2:30 PM
Typically people are burnt out after a day and a half, thus the shorter day on Tuesday. But feel free to hang around and hack or continue the discussions.
Given that we have ~40 people, it will be difficult to have a productive conversation with only one track because some people will get bored with the current topic and such. Therefore I suggest we hold hold full-group sessions punctuated by breakouts of two or more concurrent threads (T1, T2, etc.). During the multi-threaded times, people can move back and forth as they please for discussion, hacking, interop testing, a change of pace, etc. We’ll work out the final details in real time.
For the full-group sessions we may use the fishbowl approach.
For several of the sessions, I’ve provided URLs for background reading.
Lunch and beverages are included and will be served in the room.
9:30 – 10:00
Introductions, logistics, agenda bashing
10:00 – 11:00
T1: Interop testing setup + discussion about online testing
T2: XMPP 101 + general Q&A to bring newbies up to speed
11:00 – 12:00
We have ~40 people. If 6 people present, that’s 10 minutes each including Q&A. If 12 people present, that’s 5 minutes each. And so on. Any volunteers to present? If not, I’ll volunteer you at the summit! I’m particularly interested in short talks about problem areas that we need to focus on during the rest of the summit (or afterwards).
12:00 – 1:00
Semi-working lunch of sorts. Wander off, stick around, hack code, check email, post photos, blog about how much fun you’re having, update your GTD app with action items, whatever.
1:00 – 2:00
Note: we will use these threads as partial input to the HTTP+XMPP “hybrid” discussion at 2:00.
T2: Server/component interactions
how to implement protocols like pubsub, pep, and MUC as external components?
how can components access information like rosters and presence?
how to access or share component services in a federated manner? authorization of components or remote users
2:00 – 3:00
Full-group session on hybrid technologies. No, that’s not gas and electric, it’s HTTP + XMPP. Sub-topics include:
- When to use HTTP, when to use XMPP?
- OAuth (see XEP-0235)
- REST and XMPP (see here , here, here and here)
- Shared rosters / communities
3:00 – 4:00
T1: Jingle I (identify open issues for push to Draft)
T2: Pubsub I (general discussion to identify open issues and apply insights from earlier in the day)
4:00 – 4:30
Wrap-up, feedback, logistics, planning for day 2
9:30 – 10:00
Day 1 summary, logistics, agenda bashing
10:00 – 11:00
T1: Jingle II (discuss additional use cases such as SRTP and early media)
T2: PubSub II (discuss uses in hybrid technologies, federation of information exchange)
11:00 – 12:00
T1: Security, spam, etc.
topics: server to server federation, TLS+dialback, TLS+SASL, abuse prevention, end-to-end encryption
T2: Mobile optimizations
12:00 – 1:00
1:00 – 2:00
- What problems are we facing?
- What new application spaces are of interest?
- What do we need to focus on going forward? (see XSF Roadmap)
2:00 – 2:30
The room number is E142.
You do not need to register for OSCON in order to participate in the XMPP Summit. OSCON is a great conference and we encourage you to attend! However, if you want to participate only in the XMPP Summit, you MUST sign in for a free “floor pass” with O’Reilly when you arrive at the convention center.
For transportation, use Portland’s MAX (light rail) service. The Convention Center stop is your friend.
As at XMPP Summit 4, the XMPP Standards Foundation will again pay hotel costs for any elected XSF member who attends the Summit. To take advantage of this offer, please make arrangements to stay at the Marriott City Center (see this message!) and contact Peter Saint-Andre so he knows to pay for your room and can help arrange room sharing.
During the summit itself, we will use the firstname.lastname@example.org chatroom as a backchannel for discussion, information sharing, complaints, questions, etc.
As always, the XSF will host one social event (dinner or somesuch) and we will also have many opportunities to meet in the evenings for some good Portland beer.