Chaos Computer Club - archive feed

Auch in diesem Jahr sammeln Oliver und Michael die Themen, Kuriositäten und Aufreger des vergangenen Open Source-Jahres auf und diskutieren gemeinsam mit dem Publikum auf der Open Source Couch.

Auch in diesem Jahr sammeln Oliver und Michael die Themen, Kuriositäten und Aufreger des vergangenen Open Source-Jahres auf und diskutieren gemeinsam mit dem Publikum auf der Open Source Couch.

about this event: https://programm.froscon.org/2022/events/2761.html

Albert Einstein's quote "If you want to know the future, look at the past." couldn't be more accurate today. Many young software engineers and graduates today were born in the early 2000s and only know the struggles of early software engineering from their older colleagues, the vintage computing community or abandoned books. Further, many developers from the early 90s are retiring now and there is a danger of losing important knowledge.

In my presentation we will travel back 30 years and look at how software was built from 1990 to 2020. Not in theory, but with practical examples including screenshots and actual production code from the era.

[1991] "Apps" ;) for Windows 3.11 with Visual Basic 2.0

[1996] The first baby steps in "Web development"

[1997] "Mobile Apps" with C++ and PalmOS

[1999] Writing code for the last MacOS (Version 9)

[2000] Arrival of the HTML coder ;) Web development goes mainstream

[2002] C# for Windows & Windows Mobile "App development"

[2003] C++ on Linux: building everything imaginable

[2005] Apache, PHP, MySQL becomes mainstream

[2008] Birth of "The Cloud": Developing with Google App Engine

[2010] "Mobile Apps" for everyone! Building on iOS, Android & Blackberry

[2012] The great merge conflict: Git sends SVN, CVS & HG to the history books

[2015] Cloud & Software-as-a-Service: Goodbye InstallShield Wizard

[2018] Serverless & Infrastructure-as-Code: Goodbye operating system

[2020] JavaScript! How did you even survive 25 years?

Sit back, relax and enjoy the ride while we fire up the flux capacitor to look at 30 years of software development and archeologically explore software history.

I have experienced much of the software development history myself or through my father who built software from the 80s to the 90s. Given the time, the presentation will not go into every detail but give a glimpse and an immersion into the yesteryear of software development. It is supposed to be an insight into people interested in software development and history as well as those who might be interested to discover more about vintage computing, especially programming. While vintage computing is becoming more and more popular, vintage programming is still in it's infancy.

about this event: https://programm.froscon.org/2022/events/2730.html

The Small Device C Compiler (SDCC) is a free compiler targeting various 8-bit systems, including common microcontroller (µC) architectures.

The SDCC-STD-UX project funded by the Bundesministerium für Bildung und Forschung aims to improve standard compliance in SDCC, in particular support for current and future C standards.

SDCC targets common 8-bit µC architectures, such as the MCS-51, STM8, S08, Rabbit and Padauk, as well as some architectures now mostly relevant to retrocomputing or -gaming, such as Z80 and SM83. As a C compiler, SDCC aims to support current and future C standards, but is not up to the level of GCC or clang. For debug information, there is some basic support for ELF/DWARF. This summer, the Bundesministerium für Bildung und Forschung via the Prototypefund funds the SDCC-STD-UX effort to improve standards compliance and usability in SDCC. This ngoing effort has already resulted in substantial improvements in support for C standards that will be in the future SDCC 4.3.0 release.

about this event: https://programm.froscon.org/2022/events/2819.html

In den letzten Jahren wurde die openSUSE-Infrastruktur deutlich verbessert. Aber ist sie jetzt perfekt? Natürlich nicht - sonst hätten die Heroes (= openSUSE Admin-Team) Langeweile, und ich könnte diesen Vortrag nicht halten. Wo Leute arbeiten, passieren natürlich auch lustige[tm] Dinge. Bringt bitte Euer eigenes Popcorn mit ;-)

about this event: https://programm.froscon.org/2022/events/2780.html

Tui Widgets ist eine von Grund auf neu entwickelte c++ Library. Sie stellt flexibel anpassbare Elemente zur Entwicklung von Terminal User Interfaces bereit. Dabei legen wir Wert auf eine Benutzerinteraktion, die sich analog zu Desktop Anwendungen verhält.

Dieser Vortrag gibt eine Übersicht über das Framework und demonstriert anhand einer Beispielanwendung, wie das Framework verwendet wird.

Auf der vergangenen FrOSCon hat Martin breites termpaint vorgestellt. Darauf aufbauend zeigen wir euch dieses Jahr Tui Widgets.

Es kombiniert klassisches Look and Feel in der Tradition von Turbo Vision mit QtCore als Basis für Widgets und Event-Loop.

Dabei werden die Widgets über Layout-Manager angeordnet, die auf Veränderungen der zur Verfügung stehenden Fläche reagieren können.

Es stehen Elemente für Texteingabe, Radio- und Checkboxen, Buttons, Listen und Menüs genauso wie Fenster zur Verfügung.

about this event: https://programm.froscon.org/2022/events/2743.html

It’s easy to see how OpenStreetMap could be leveraged to improve the completeness and freshness of government geospatial datasets. So why aren’t all governments using OpenStreetMap? In the US, the ODbL license has prevented government agencies from using the data. Public Domain Map aims to resolve this (and other challenges) by providing a workflow that allows contributions to be used in both OpenStreetMap and public domain US Government databases. We will share the journey of Public Domain Map, and importantly, how the project is bringing together US federal agencies and open source contributors to meet this goal.

about this event: https://2022.stateofthemap.org/sessions/CFVMU7/

Language barrier and the default to English puts non-English speakers at a systemic disadvantage throughout open mapping communities and humanitarian open mapping activities resulting in significant missed participation and impact. We held experimentation on language translations of key resources identified by collaborators coming from local OSM communities and we hope to share the findings in this talk.

We believe that language localization will enable inclusion and participation of underrepresented groups in mapping, dialogues and other humanitarian open mapping activities.

We ran small experiments with local contributors to test how localisation of resources could work in the main languages of 3 priority countries (Vietnam, Madagascar, Mozambique) and we hoped its insights would inform a self-sustainable Localization Strategy for these communities and beyond. However, the documented findings are not sufficient due to challenges encountered (including communication and technical barriers, difficulty with monitoring and evaluation, among others) during the course of the research. Hence, opportunities and recommendations will be presented for future work to explore this theme.

OSM Diary post on the launch: https://www.openstreetmap.org/user/arnalielsewhere/diary/397844

about this event: https://2022.stateofthemap.org/sessions/3MMV93/

During the 2019-2020 pilot supported by Microsoft, 18 million building footprints were automatically extracted from satellite imagery for all of Tanzania and Uganda. HOT found that on average, mappers working without AI assistance could map between 1000-1500 buildings per working day. For areas with high-quality AI output, providing mappers with AI-generated building footprint suggestions increased this rate to up to 2500-3000 buildings per day approximately doubling the rate at which building data could be added to OpenStreetMap, which is the crucial link for making it available to the humanitarian information management community.

While doubling mapping efficiencies (100% efficiency gain) are promising, one of the greatest challenges is making sure data is converted from AI/ML to OpenStreetMap in a rapid yet responsible community-centric way (respecting existing data contributions already in OpenStreetMap). This project enabled us to take the ‘next step’ after receiving the building predictions from Microsoft by building better tools for data conflation. This is expected to dramatically reduce manual intervention. By doing this, human mappers can focus their time and skills on value-added activities: ground-truthing and validating predictions and adding local knowledge to the map not visible from satellite imagery (such as place names, location of key lifeline infrastructure, etc.

We’ll describe our mapping workflow and progress updates for Kenya and Nigeria, and the specific challenges met with this dataset extracted through machine learning will be explained. Considering the growing availability of such AI-related datasets, we’ll review common errors and how we adapted to them and to other issues such as imagery offsets, heterogeneity of existing data and other context specific challenges. Eventually we’ll propose recommendations regarding this type of editing and aspects to consider before starting such imports and how to get the community involved.

about this event: https://2022.stateofthemap.org/sessions/GNEJ9G/

This session will provide an introduction to the OpenStreetMap operations team, what OpenStreetMap.org services we are responsible for building and maintaining.

Grant recently became the OpenStreetMap Foundation's first full-time employee. Grant will present how he is helping improve reliability and security of the project's technology and infrastructure.

Grant will detail how the Operations team are modernising the project's infrastructure by reducing complexity, paying-down [technical debt](https://en.wikipedia.org/wiki/Technical_debt), while reducing the need to maintain [undifferentiated heavy lifting](https://www.factoftheday1.com/p/december-23-undifferentiated-heavy).

If you’re interested in what powers OpenStreetMap and make it tick, come to this session.

about this event: https://2022.stateofthemap.org/sessions/D8XYDN/

QGIS is one of the most used Opensource GIS software with some native functionalities to work with OSM data. Either with raster layer as a basemap, or with vector, QGIS can deal with OSM data. Depending on the amount of data to work with, the need to "refresh" the data (from the main OSM database), the extent of the coverage, different plugins or technologies are possible.

This presentation will try to give an overview how it's possible to use OpenStreetMap data according to different situations (Geocoding, TMS/WMS, OverpassAPI, PostgreSQL…). The presentation will show how you can contribute to QuickOSM to add some default « mappreset » to QuickOSM on GitHub.

about this event: https://2022.stateofthemap.org/sessions/AKYJPG/