XMPP

Software

Clients

Servers

Libraries

Info

About

Discussion

Overview

Roadmap

XSF

Weblog

Protocols

Core Stack

Extensions

Internet-Drafts

RFCs

Resources

Certificates

Registrar

Schemas

XMPP Summit

Sponsors

AG Software

Cleartext

DreamHost

Google

HP

Jabber Inc.

Jive Software

Process-one

USSHC

Wimba

JSF Board Meeting

Date: 2002-12-03 @ 16:30 UTC
Location: 1899 Wynkoop Street, Denver, CO, USA
Alternate Participation: Conference Call
Scribe: Peter Saint-Andre, Secretary of the JSF

Roll Call

At 16:33 UTC, roll call was taken. The following individuals were in attendance:

All Board members were in attendance. Quorum requirements were met.

Discussion

  1. Jabber Trademark

    Discussed the Jabber Trademark Position Statement and the Letter of Intent formulated by Tony. Agreement that these documents generally meet our needs. Peter raised a question about the exact timeline for a review with regard to trademark transfer and Michael raised a question about the wording of the review procedure. Tony will make slight changes to the documents and they will be approved in an interim meeting before the next scheduled meeting in January.

  2. XMPP WG

    Jer, Tony, and Peter reported on the success of the XMPP WG meeting at the 55th IETF in Atlanta, providing details about the priorities of the WG, its projected timeline, issues related to backwards compatibility (desirable but not the top priority of the group), and interaction with the SIMPLE WG (especially the "Jabber sessions" Internet-Draft for initiating an XMPP session from SIP devices).

  3. Marketing Committee

    Michael and Marco reported on the work of the Marketing Committee, including the draft JSF Sponsorship Program and JSF Grant Program formulated by Michael Bauer, Iain Shigeoka, Harold Gottschalk, et al. Several Board members expressed concern that presenting potential sponsors with two programs to support might be confusing and lead to one or the other being underfunded. Agreement that it is best to clearly communicate why sponsors should support the JSF, including how sponsorship money is directed (e.g., ongoing expenses, in-person meetings of the Jabber Council, compliance testing program, etc.). Discussed possibility of funding, through a grant program, the creation of running code (a la Source Exchange), but decided that if code projects are supported, they should be related more to research and development than the creation of production-ready components. Consensus reached that there should be one sponsorship program with multiple levels of support, and the ability of larger donors to earmark a relatively small percentage (perhaps 10%-20%) of their monies to certain pre-defined R&D projects (e.g., whiteboarding, pub-sub, and other initiatives approved by the JSF). Michael will take these results back to the Marketing Committee and work to generate a sponsorship program definition.

  4. Compliance Committee

    Jeremie Miller reported on the Compliance Committee. As captured on the wiki, the focus seems to be on minimal compliance for now (the basic wire protocol, not UI or advanced features). This minimal compliance may be "XMPP Compliance", with "Jabber Compliance" comprising one or more levels above that (probably multiple levels). Jer will bundle the existing wiki information (etc.) into a document for review by the Compliance Committee. The intent is to create a test bot or component against which developers can unit-test, then save the results into a database (perhaps with a reporting function). This will enable client developers (open-source and commercial) to ensure that their software is compliant before submitting it for official compliance testing and certification by the JSF. Pricing levels for certification of commercial software yet to be determined, but should be relatively inexpensive to encourage certification (though high enough to cover our costs).

  5. Official Liaison Role

    Discussed the desirability to deputize individuals as official liaisons or "ambassadors" to other other projects/initiatives/organizations if necessary and appropriate (examples might be liaisons to the Apache Software Foundation, Java Community Process, etc.). If an individual is to have an official role (including the right to represent the JSF with relation to another organization), the individual needs to be accountable and the Board needs to have some measure of oversight. Therefore the Board must approve any such role, and will do so on a case-by-case basis.

Resolutions

  1. Resolved: that the Board of the JSF approve the Letter Of Intent for re-licensing the Jabber Trademark and eventually transferring the trademark to the Jabber Software Foundation.

    Action: Deferred pending slight changes to the LOI.

  2. Resolved: that the Board of the JSF must approve the role of a formal liaison from the JSF to any other organization.

    Action: Approved

New Business

  1. Tony informed the Board of the Messaging and Presence Interoperability Consotrium (MPIC), a group of carriers, service providers, and enterprises that will act as advocates for interoperability in the IM and presence arena. Still embryonic but Tony is participating and may ask to be named as an official JSF liaison to MPIC.
  2. Peter reminded the Board that applications for new members will be accepted again from January 1 to January 10.
  3. Michael will submit a formal budget shortly.
  4. Peter relayed concern from several JSF members that it may be counterproductive for Board members to lead committees such as the Marketing and Compliance committees. The feeling of the Board is that ideally this would not be the case but that no hard-and-fast rule is required.

Adjournment

The meeting adjourned at 18:32 UTC.