We're hiring!
*

Cambridge XMPP Sprint

Maxime Buquet avatar

Maxime Buquet
August 30, 2018

Share this post:

Reading time:

Earlier this month, on August 18-19th, was held the first developer event in the XMPP community for a long time.

The idea came up at the Gulaschprogrammiernacht, in Karlsruhe earlier this year, talking with Daniel Gultsch, and JC Brand. We gathered there to work on an implementation of the OMEMO encryption mechanism for Converse.js, and Poezio. Converse.js is currently seeing the changes merged. It’s taking a bit more time for Poezio, but we’ll get there.

JC mentioned sprints organised by the Plone community, and I felt that was something we were missing for XMPP. While the XMPP summit is held every year before FOSDEM, it is often more oriented towards protocol discussions. Developer events are scarce.

I set a goal for myself to start a movement in the community, gather interested people, and work together to improve the ecosystem.

The first event – of this hopefully long series of events – was held this month, sponsored by my employer, Collabora, in their UK offices in Cambridge!

Who attended

And remotely:

Objectives

We started the sprint with a short standup, to discuss ideas gathered during the previous weeks online, and to narrow the focus to a few feasible items. At this point it became clear that User Experience (UX) would be an important topic during the weekend, as it is also within the XMPP community of late.

Here is roughly what was mentioned, and what we planned to work on:

  1. Bookmarks: Sync Private XML bookmarks with PEP ones.
    XMPP has different standard places to store bookmarks, and this has often proven to be a painful experience to the user, when using different clients for example. The objective here was to transparently synchronize both stores, so that the user gets an overall nicer experience.
  2. Message Attaching and Reactions.
    Message Attaching defines a way by which one can indicate that a message is semantically related, “attached”, to an earlier message in the discussion. This can be useful for reactions, for example, or even for previews of links.
  3. In-Band Registration in clients that don’t support it, namely Dino and Poezio.
    In-Band Registration is a mechanism that allows clients to provide an interface to create accounts on servers that allow it. This way the user doesn’t have to go through multiple hops to start chatting with their friends.
  4. Consistent color generation.
    This specification aims at providing algorithms that will be used to generate deterministic colors, so that they stay consistent across clients, and thus help with recognition, for nicknames in groupchats, for example.
  5. Hats.
    Hats allow for customised roles and affiliations in chatrooms, an extension of the usual roles and affiliations. They can be used as regular “titles” that are displayed to other users, (e.g., “Teacher”, “Student”, “Developer of XYZ”), but can also carry permission information. The current specification needed reworking as it has been left with lots of TODOs, and was not really finished nor implementable.

Hard working developers

Accomplishments

Not everything that was mentioned on the saturday morning was worked on, but we did manage to get quite a few things done. This was also the opportunity to discuss about various topics.

As this is also something I would like to encourage, I am happy to say that first-time XMPP users were able to contribute on projects, by providing feedback as well as patches.

Here is a non-exhaustive list of issues/topics we worked on:

Conversations

  • Use PEP Bookmarks if urn:xmpp:bookmarks-conversion:0 is announced. commit
  • Experiments with Consistent Color Generation:
    Disabled by default variant that uses HSLUV instead of YCbCr. HSLUV provides more uniform colors and also ‘nicer’ colors by default. commit
  • Updated Conversations Compliance Checker help for Prosody: pull/6

Converse.js

Dino

Packaging

Poezio

Prosody

XEPs (specifications)

  • Synchronisation between vCard-based and PEP avatars: pull/700
  • Started XEP for synchronisation between Private XML and PEP bookmarks
  • Message attachments XEP updated: pull/696
  • Started writing of a counter-proposal XEP for Hats.

Original information about the event is now listed in the wiki.

I would like to thank everybody who participated, helped organise the event, and made all this possible. Thanks Collabora again for sponsoring the event and providing the venue.

What’s Next

Talks of organising a next sprint this year in Düsseldorf, or Paris, are already happening. I would also like to encourage anybody who wants to organize similar events in their region. If you are interested and want to help organize, or participate, please join the chatroom for more information.


Visit Maxime's blog.

Related Posts

Related Posts

Comments (0)


Add a Comment






Allowed tags: <b><i><br>Add a new comment:


Search the newsroom

Latest Blog Posts

Automatic regression handling and reporting for the Linux Kernel

14/03/2024

In continuation with our series about Kernel Integration we'll go into more detail about how regression detection, processing, and tracking…

Almost a fully open-source boot chain for Rockchip's RK3588!

21/02/2024

Now included in our Debian images & available via our GitLab, you can build a complete, working BL31 (Boot Loader stage 3.1), and replace…

What's the latest with WirePlumber?

19/02/2024

Back in 2022, after a series of issues were found in its design, I made the call to rework some of WirePlumber's fundamentals in order to…

DRM-CI: A GitLab-CI pipeline for Linux kernel testing

08/02/2024

Continuing our Kernel Integration series, we're excited to introduce DRM-CI, a groundbreaking solution that enables developers to test their…

Persian Rug, Part 4 - The limitations of proxies

23/01/2024

This is the fourth and final part in a series on persian-rug, a Rust crate for interconnected objects. We've touched on the two big limitations:…

How to share code between Vulkan and Gallium

16/01/2024

One of the key high-level challenges of building Mesa drivers these days is figuring out how to best share code between a Vulkan driver…

Open Since 2005 logo

We use cookies on this website to ensure that you get the best experience. By continuing to use this website you are consenting to the use of these cookies. To find out more please follow this link.

Collabora Ltd © 2005-2024. All rights reserved. Privacy Notice. Sitemap.