The results of the Open Source Impact Study tasked by the European Commission have been widely discussed mainly because of its numbers. Though being announced just now, the study identified for the year 2018 a contribution of 0.4% to the GDP worth EUR 63 billion by FOSS, if measured by the increase in commits. 10% more contributors would even raise the GDP of the European Union by 0.6% (EUR 95 billion). The overall cost-benefit ratio is estimated with at least 1:4.
But it gets even more interesting, when looking into the results of the accompanying survey covering about 900 stakeholders (mainly companies) from all around Europe.
For them, incentives for using and investing in Open Source have been, sorted by relevance:
finding technical solutions
avoiding vendor lock-in
carrying forward the state of the art of technology
As benefits they have seen:
support of open standards and interoperability
access to source code
independence from proprietary providers of software
Within the participants the cost-benefit ratio has been estimated even with 1:10.
The current circumstances also forced conferences (those gatherings with really large audiences) completely into cyberspace. Some sticked with traditional approaches to stream talks via off-the-shelf videoconferencing applications and built upon the integrated very limited interaction features offered by these poor proprietary tools. Others have gone complete new ways and brought fascinating and well working concepts on how to still successfully connect the crowds to enable lively conversations and facilitate the exchange of knowledge and experiences in a distant environment.
Let’s start with rc3 and its virtual conference venue in form of rc3 world, implemented with Work Adventure. In a pixel-2D-adventure-style you could walk around the area and as soon as you are approaching other characters, a live audio and video stream with those humans or other live forms controlling the character would open. Limited to 4-5 persons at a time, it allowed you to talk directly with each other – face to face. Due to the limitation of participants you were still able to have a working conversation.
Somehow you needed to get used to having an unexpected and sudden interaction with one and another – on live video, but still it brought back the heavily missed opportunity to get in personal touch with other participants who are sharing possibly similar interests.
The FOSDEM 2021, the worlds biggest conference on Free and Open Source Software usually taking place in Bruxelles, had for me a very convincing overall concept. The organizers and infrastructure artists have done a tremendous job that allowed for the most impressive conference experience so far and for long. Naturally and purely based on Free Software, at its core matrix, element, and Jitsi.
How did it work and what was so great about it?
Presentations of specific areas of interest had been summarized in virtual rooms with a fixed agenda, like in most physical conferences. Participants logged into a chat infrastructure which represented the rooms by group conversations. You would simply join the room(s) that you are interested in and could start texting with each other and the speakers like on IRC. Talks had been recorded beforehand and where automatically started – by the computer (systemd) – at their scheduled time. Its audio and video were streamed right above your chat window. When the talk ended, the Q&As were streamed live for a fixed amount of time within that room until the next talk started auto-playing according to schedule. During that first part of the Q&A session of a talk, moderators where clarifying upvoted questions and comments from the chat and interacting realtime with the presenters. Those interested could then continue discussing with the speakers and further extend their conversation by switching to a separate room. So per talk you had a dedicated room for the second part of the Q&A that would open shortly after and even allowed anyone there to interact live via audio and video.
In sum that meant that you could check the schedule for topics you are interested in, connect at the announced time and be sure to really listen to that talk instead of watching tech staff doing mic checks or heavily delayed earlier talks whilst being unsure about if and when the one you came for would actually start.
In addition the highly valued Q&A and following backstage (and off the record) conversations could still take place without interrupting or being interrupted by the subsequent talk.
Just impressive and so useful! Thanks a lot to all who made this happen and work that well! These concepts are now here to stay, even when conferences will hopefully resume soon back in the physical world.
A few days ago the oral hearing of the lawsuit between Oracle and Google were held at the U.S. Supreme Court, after it had been delayed by COVID-19. McCoy Smith shares his observations and interpretation in a detailed post “Oracle/Google” at Lex Pan Law. The litigation is over the copyrightability and if so infringement of certain parts of Java (mainly APIs) that were used within Android. If Oracle wins it will have significant impact on the whole software world and especially Open Source. Ultimately any API (use) would become subject to copyright.
I started my digital photography life with a Nikon D80 and Lightroom 1.0 quite a while ago (2007). When Adobe stopped selling copies and only provided subscription options was one of the moments it became very clear that an alternative is needed. Let’s not talk about Lightroom CC, its unstable desktop app, and a recent user nightmare.
To be independent from the business needs of a company, the only option is to go for an alternative that is licensed under an Open Source license. With that preference in mind and if it is about RAW processing, you have the choice between digiKam, RawTherapee, and darktable.
I was following darktable since a few years. The 2.x versions have not really been working for me. In contrast the releases of 3.0 and 3.2 have been milestones in growing darktable into a serious and easy to use – not to say even more mature – alternative to Lightroom and it is time to do the final switch. Now or never.
To share it upfront: I did not get disappointed nor frustrated by this decision. I am just wondering, why the hell did I not switch earlier?
It has been instantiated for the sole purpose of trademark management (and enforcement?) for Open Source projects, who are said to be not well positioned to care by themselves. For a start Google assimilated their own projects: Angular, Istio, and GerritCode Review. Own Projects? Oh well, at least for Istio – that was co-developed with IBM – they now clarified who has ownership of its trademark.
In their introduction statement they claim: “[…] Accordingly, a trademark, while managed separately from the code, actually helps project owners ensure their work is used in ways that follow the Open Source Definition by being a clear signal to users that, “This is open source.” […]”
Josh Simmons, the president of the Open Source Initiative (OSI) maintaining the referenced definition has a diplomatic statement to that, which also serves well as a summary: “Of course, OSI is always glad when folks explicitly work to maintain compatibility with the Open Source Definition. What that means here is something we’re still figuring out, so OSI is taking a wait-and-see approach.” 
Or is this yet another project for the Google Cemetery because the Open Source community is not that into trademarks as cooperations are?
There are more detailed summaries and discussions:
In the golden age of Open Source compliance offerings, one of the key marketing argument still appears to be: “The General Public License (GPL) is sooo risky. In case of GPL infringement, you will have to release all of your code – speak your intellectual property (IP) – under the same terms. Take our license scanner as we are the best to protect you against such nightmares.”
That statement simply is not correct. But very effective if you want to sell your services. Which company wants to be forced to release its valuable IP into the public only by not following specific license terms?
His general understanding of one of the basic principles of Free Software and the GPL – reciprocity – speaks of great intellectual power. However this muddle-headed theory in total is utterly wrong but still persistent today serving as one of the main arguments to sell license compliance offerings.
Even infringing the terms of the GPL will never force you to put your own source code under the same license. Simple as that.
Sure, in the worst case you have violated a software license. In this aspect there is no difference between the GPL or any other even proprietary license. Copyright infringement claims are caused by
the actual violation of the license and
the unlicensed use of software.
You have to cope with its consequences. Legal remedies are
punitive damages and
injunction to not distribute your product any further.
Wenn man von einem Chaos Communication Congress zurückkehrt, wird man oft interessiert gefragt: Und, wie war es? Erzähl mal, um was geht es da eigentlich?
Übervoll mit Eindrücken und übermüdet trotz regelmäßigen Mate-Konsums fällt es schwer, auf Anhieb passende Worte für einen allgemein verständlichen Abriss zu finden.
Wenn auf diese Art keine Zusammenfassung möglich ist, würde man als nächstes eigentlich zum mobilen Endgeräte greifen, um zumindest die bildlichen Impressionen für sich sprechen zu lassen. Doch halt, dort wird der Grundsatz noch ernst genommen, nur Photos anzufertigen, wenn alle auf dem Bild abgebildeten Personen damit einverstanden sind. Dementsprechend leer ist die eigene Bildergalerie.