Extended Conversation

We started with Bear and Joe giving a brief welcome and then we went around the room and alloed the attendees to introduce themselves. After the introductions we worked out the Agenda using the barcamp style of posting topics to the white-board and haggling over which order to work thru them.

Since the focus turned out to be almost all interop testing the group set up infrastructure with Jack E. helped by setting up a local CA Server and Joe setting up both DNS and DHCP while the great guys from &yet provided network hubs and patch cables. This allowed our testing to be done all on a private network, using example.com as our base DNS domain.

Once the servers were up and running, we then retrieved the appropriate certificates that Jack E. had created and installed them into each server. This took longer than expected, as getting each server/OS to import the CA certificate to the appropriate trust store was troublesome.

Once basic private network features were up and each server being tested was online, we then tried to login to each server with PSI and Gajim (they just happened to be the most prevalent multi-account supporting clients we all had) and then moved on to testing BOSH and CORS. BOSH setup and testing continued until the break for lunch.

While some folks were getting BOSH testing working (i.e. once Bear finally learned how to read the Prosody docs!) Jack was also checking that S2S unencrypted connections between the servers that were ready to test was correct at the wire level. He spent a lot of time in wireshark!

After lunch we had short presentations from Joe on some of the new XEP’s he would like to see worked on (especially Carbons, XEP-0280) and then we had some demos of &yet’s browser-based client , DragonForce and OneSocialWeb.

(editor’s note: apologies for this appearing now, it got stuck in the publish queue and I did not notice it until I went to publish the Day One Summary that follows. d’oh!)

Next week (July 19th and 20th 2010) the XSF will be having the 9th XMPP Summit at the Oregon Convention Center courtesy of the great folks at O’Reilly who allow us to take over a room during OSCON.

Details can be found on the wiki page.

As in prior years, one of the primary focuses will be an Introduction to XMPP session for anyone wishing to learn (or improve) their XMPP knowledge. One of the primary goals this session will be to perform some client/server interop testing but other break-out sessions always pop up as folks start to get together.

If your going to OSCON 2010, or are in the area, please do stop by.

This is the fourth and last in a series of podcasts made at FOSDEM in Brussels, Belgium.

Today, we are listening to Simon Tennant.

Simon is running BuddyCloud, a federated social network based on XMPP.

This is the third in a series of podcasts made at FOSDEM in Brussels, Belgium.

Today, we are listening to Florian Jensen.

Florian is serving on the XSF Board of Directors, and runs flosoft.biz, a hosting company.

This is the second in a series of podcasts made at FOSDEM in Brussels, Belgium.

Today, we are listening to Dave Cridland.

Dave is serving on the XSF Council, and is working on M-Link, the XMPP server by Isode.

This is the first in a series of podcasts made at FOSDEM in Brussels, Belgium.

Today, we are listening to Fabio Forno.

Fabio contributes to many codebases, such as Twisted Matrix, Lampiro, Araneo, proxy65, and more.

As of 1900 UTC Monday, Google has published the list of accepted project for the Google Summer of Code and I’m very happy to report that four of the proposals to the XSF were accepted!

Congratulations to Nicolas, Tobias, Zhenchao and Zhiwei for braving the process and getting accepted!

Now the real work starts ;)  — a great article to read is from the GSoCMentoring series

I’m looking forward to working with them and their mentors in making this a great Summer of Code!

Hey everyone!

Less than 3 weeks left until the XMPP Summit #8 comes to Brussels.

This year, we’ve got something new! Nokia has generously offered to sponsor a mobile XMPP developer challenge.

What does that mean?

Starting from NOW, you can start writing a mobile application for ANY Nokia platform (Maemo / S60v3 / S60v5 …).

The requirements are:

• The program must be FREELY available; OpenSource is preferred.
• The application needs to be demoed on a Nokia Phone (we have demo devices on location) on the XMPP Summit (Monday). If you are not attending the Summit, find someone who is, and can demo / explain the app, and collect the prize.
• Limit of 1 application per attendee.
• Substantially new code, as decreed on the day by the judges. (If you have questions, the judges will give guidance, but the final decision will be made on the day)
• Judges aren’t eligible.
• And of course: The application needs to use XMPP in some way.

The judges are: Jack Moffitt (XSF Board Chairman); Kevin Smith (XSF Council Chairman); Kristian Luoma (Nokia)

So what can I win?

We have one Nokia N900 generously sponsored by Nokia which the judges will hand over to the best application.

We will also have a second prize, whose winner is chosen by all the attendees (participants excluded). This prize consists of 2 XMPP books (XMPP: The Definitive Guide; Professional XMPP Programming with Javascript and Jquery) and an official XMPP T-Shirt.

So, open up those text editors and start coding, and good luck!

It’s well-known that XMPP technologies emerged from the open-source server project first released by Jeremie Miller in 1999, as well as the combined software/operator community that grew up around the server.

In the early days, “Jabber” meant many things: Jer’s server, the protocol used between clients and servers, the server network, the community in general, even a company called Jabber.com (then Jabber Inc., purchased by Cisco Systems in late 2008). Over time we have worked to disambiguate the terms. Thus Jer’s server was renamed jabberd and the protocol was renamed XMPP.

However, the relationship between the jabber.org and xmpp.org domains has remained a bit nebulous. Several years ago, the Board of Directors of the XMPP Standards Foundation clarified the matter by stating that the jabber.org domain was a community effort hosted on XSF machines but operationally independent of the XSF. That clarification was never formally announced, but the decision was recently re-affirmed by the current Board so now seems like an appropriate time to make the distinction more public.

The basic division of responsibilities is this: the XSF focuses on the “rough consensus” part of “rough consensus and running code” by defining the core protocols used by the entire XMPP community, as published at the xmpp.org website; by contrast, the Jabber.org team focuses on the “running code” part by offering a popular, XMPP-based, real-time communications service. This focus was incorporated into the recent redesign of the jabber.org website (which now is dedicated to information about the jabber.org IM service), and has long been evident at the xmpp.org website as well.

Now you know!

–stpeter

The XMPP Standards Foundation has helped support a number of open-source projects through Google’s Summer of Code program over the years. Although the XSF is not participating in the Google Summer of Code this year, a number of XMPP-related projects have been accepted by other mentoring organizations…

On the JabberFr forums, “Misc” posted the full list:

• Pidgin:
  • XMPP – libpurple transport, allowing servers to offer gateways to all the IM networks that Pidgin (or Adium) supports
  • Privacy Rewrite, giving users powerful controls over “XMPP firewalling”
  • Telepathy prpl, integrating Pidgin’s powerful Purple library with the GNOME Instant Messaging and Presence framework
• Apache Foundation:
  • Extend the Vysper XMPP Server/Client with the publish-subscribe XEP (XEP-060)
• Python Foundation:
  • Gajim: Whiteboard Implementation
  • Adding support for server-side history and roster versioning in Gajim
• Gnome :
  • GNOME-Games + Telepathy: Play GNOME-Sudoku with your IM contacts
  • Implement Music Sharing in Banshee using the Telepathy API
• KDE :
  • VoIP client for KDE (revive KCall)
  • KDE – Conversation Logging Framework
  • Turn Kopete chat window into a library
• Maemo :
  • IM Client For Canola Using Python-purple

At the XSF, we’re tremendously excited to see so much implementation of cutting edge technologies in so many widespread projects. It’s a testement to the innovative nature of the XMPP community, and we’re looking forward to seeing – and using – the results.

Article by Misc, translated by Nicolas Vérité, edited by Dave Cridland.