Difference between revisions of "Interop Event"

From XMPP WIKI
Jump to navigation Jump to search
Line 37: Line 37:
 
=== Logistics ===
 
=== Logistics ===
  
The JSF will charge $200 per person in order to cover costs associated with hosting of the event. This fee will be waived for open-source developers. Please make payment via PayPal to the address "paypal@jabber.org".
+
The JSF will charge $200 per person in order to cover costs associated with hosting of the event. This fee will be waived for open-source developers. Please make payment via PayPal to the address "paypal@jabber.org" or by check to JSF P.O. Box 1641 Denver CO 80201 USA. You may also pay in person at the event.
  
 
Although originally we thought space might be limited because of the venue, that is no longer the case. Multiple participants from participating companies are welcome.
 
Although originally we thought space might be limited because of the venue, that is no longer the case. Multiple participants from participating companies are welcome.

Revision as of 14:51, 8 June 2006

The Jabber Software Foundation (JSF) will hold an XMPP interoperability testing event on July 24 and 25, 2006 in Portland, Oregon, USA. This is the same week as O'Reilly's Open Source Convention (OSCON). Details follow. Please note that this page is subject to change as further information becomes available.

Purpose

The purpose of this event is to test interoperability between multiple implementations of the XMPP RFCs (3920 and 3921). All participants will be expected to file implementation reports (in accordance with a format and template yet to be developed), which will form one input to the process of advancing the XMPP specifications from Proposed Standard to Draft Standard within the Internet Standards Process at the IETF (see RFC 2026). The other expected outcome will be a consensus set of proposed modifications and clarifications to the XMPP RFCs for discussion on the mailing list of the XMPP WG after the event concludes (see http://www.xmpp.org/xmppbis.html for provisional examples).

Focus

The main focus of this event will be server testing. Testing of clients that are in or near full compliance with the XMPP RFCs will also occur (XMPP is a client-server technology, so we need both), but given the large number of Jabber/XMPP clients it will not be feasible to test very many clients. A set of test cases will be published several months in advance for use by the participants. The test cases will focus only on protocol compliance, not scalability, reliability, ease of use, or other such factors.

This will be a small, developer-only event. No customers, no marketing people, no guano. All bugs will stay in the room.

This is not a more general developer conference. While the JSF may hold such conferences in the future, this is a small, focused, interop testing event. However, participants are encouraged to attend OSCON (same week, same city) and to get involved in Jabber-related activities there.

Logistics

The JSF will charge $200 per person in order to cover costs associated with hosting of the event. This fee will be waived for open-source developers. Please make payment via PayPal to the address "paypal@jabber.org" or by check to JSF P.O. Box 1641 Denver CO 80201 USA. You may also pay in person at the event.

Although originally we thought space might be limited because of the venue, that is no longer the case. Multiple participants from participating companies are welcome.

If you are interested in participating in this event, please contact Peter Saint-Andre directly via IM, email, or phone using the addresses listed at http://www.jabber.org/people/stpeter.shtml

Attendees

The confirmed attendees as of 2006-05-31 are:

  • Jacques Bellisant (Sun)
  • Gary Burd (Google)
  • JD Conley (Coversant)
  • Brad Fitzgerald (djabberd)
  • Gaston Dombiak (Jive Software)
  • Justin Karneges (Psi)
  • Mridul Muralidharan (Sun)
  • Mickael Remond (Process-One / ejabberd)
  • Peter Saint-Andre (JSF)
  • Alexey Shchepin (ejabberd)
  • Matt Tucker (Jive Software)

Communication

A dedicated mailing list is available for attendees and interested others (e.g., those who would like to discuss test case development). The list is publically archived.

Test Cases

Test cases for the interop event are being edited at the Interop Event Test Cases page.