Language Selection

English French German Italian Portuguese Spanish

Events: Linux Plumbers Conference and Copyleft Conference

Filed under
OSS
  • Linux Plumbers Conference 2019 Call for Microconference Proposals

    We are pleased to announce the Call for Microconferences for the 2019 edition of the Linux Plumbers Conference, which will be held in Lisbon, Portugal on September 9-11 in conjunction with the Linux Kernel Maintainer Summit.

  • Linux Plumbers Conference 2019 Call for Refereed-Track Proposals

    We are pleased to announce the Call for Refereed-Track talk proposals for the 2019 edition of the Linux Plumbers Conference, which will be held in Lisbon, Portugal on September 9-11 in conjunction with the Linux Kernel Maintainer Summit.

    Refereed track presentations are 50 minutes in length (which includes time for questions and discussion) and should focus on a specific aspect of the “plumbing” in the Linux system. Examples of Linux plumbing include core kernel subsystems, toolchains, container runtimes, core libraries, windowing systems, management tools, device support, media creation/playback, and so on. The best presentations are not about finished work, but rather problems, proposals, or proof-of-concept solutions that require face-to-face discussions and debate.

  • Source-code access for the long haul

    Corporations that get their feet wet in the sea of free software often find out that not only do they now have obligations to provide source code, but that people will actually try to access it and complain loudly if they can't get it. At the first Copyleft Conference, Alexios Zavras from Intel spoke alongside Stefano Zacchiroli from Software Heritage about how the two organizations are working together. Software Heritage's mission makes it ideally suited to host Intel's many source-code releases in a way that provides stable long-term repositories that Intel can then reference.

    This year's FOSDEM was its 19th edition, and it's now a regular and much-loved part of the European free-software year. But for the first time, the Software Freedom Conservancy organized a one-day Copyleft Conference immediately following FOSDEM in Brussels; it is intended to allow a more in-depth exploration of copyleft issues than the Legal and Policy Issues devroom at FOSDEM can accommodate.

More in Tux Machines

today's howtos

Android Leftovers

Latest From Libinput

  • libinput and tablet proximity handling
    This is merely an update on the current status quo, if you read this post in a year's time some of the details may have changed libinput provides an API to handle graphics tablets, i.e. the tablets that are used by artists. The interface is based around tools, each of which can be in proximity at any time. "Proximity" simply means "in detectable range". libinput promises that any interaction is framed by a proximity in and proximity out event pair, but getting to this turned out to be complicated. libinput has seen a few changes recently here, so let's dig into those. Remember that proverb about seeing what goes into a sausage? Yeah, that.
  • libinput and the Dell Canvas Totem
    We're on the road to he^libinput 1.14 and last week I merged the Dell Canvas Totem support. "Wait, what?" I hear you ask, and "What is that?". Good question - but do pay attention to random press releases more. The Totem (Dell.com) is a round knob that can be placed on the Dell Canvas. Which itself is a pen and touch device, not unlike the Wacom Cintiq range if you're familiar with those (if not, there's always lmgtfy).
  • Libinput 1.14 Will Support Dell's Totem Input Device
    Dell announced the Totem two years ago while the Linux support is finally getting in order. However, there isn't yet any notable applications/tool-kits at least on Linux that support utilizing this specialized input device. Red Hat input expert Peter Hutterer, who also maintains libinput, has blogged about the Totem support addition for the upcoming libinput 1.14. If you are interested in this unique input device, Peter's post has all the interesting technical bits.

Jami/Ring, finally functioning peer to peer communication client

Some years ago, in 2016, I wrote for the first time about the Ring peer to peer messaging system. It would provide messaging without any central server coordinating the system and without requiring all users to register a phone number or own a mobile phone. Back then, I could not get it to work, and put it aside until it had seen more development. A few days ago I decided to give it another try, and am happy to report that this time I am able to not only send and receive messages, but also place audio and video calls. But only if UDP is not blocked into your network. The Ring system changed name earlier this year to Jami. I tried doing web search for 'ring' when I discovered it for the first time, and can only applaud this change as it is impossible to find something called Ring among the noise of other uses of that word. Now you can search for 'jami' and this client and the Jami system is the first hit at least on duckduckgo. Jami will by default encrypt messages as well as audio and video calls, and try to send them directly between the communicating parties if possible. If this proves impossible (for example if both ends are behind NAT), it will use a central SIP TURN server maintained by the Jami project. Jami can also be a normal SIP client. If the SIP server is unencrypted, the audio and video calls will also be unencrypted. This is as far as I know the only case where Jami will do anything without encryption. Read more