Chemnitz Linux Days
event sequence
The Chemnitz Linux Days (German: Chemnitzer Linux-Tage) are an annual event focusing on Linux and free (libre) software in general. It takes place in the auditory and seminar building of Chemnitz University of Technology (German: Technische Universität Chemnitz / TU Chemnitz) in the federal state of Saxony, in the south-east of Germany. There are talks, project booths (both by community projects and by enterprises in the FOSS market), workshops, install parties, child care and playful educational lectures for the younger visitors, as well as technical help desks (Doctor Tux office). Both talks and workshops are held in German; some are also held in English, and they cover a broad variety of topics for professionals as well as entry-level visitors.
History
The first CLT took place in 1999 – a single-day event with several talks and an install party. It was attended by about 700 visitors. Since 2000 the CLT have been established as a weekend event in the first two weeks of March. The event is organized mainly by (former) students and employees of Chemnitz University of Technology, especially members of the faculty of mathematics and informatics / computer studies. Furthermore, members of Chemnitz LUG (Linux user group, part of IN Chemnitz e.V.), on whose initiative the CLT were founded, take an active part in the process, as well as external members from all around Europe. In 2017, CLT decided to sponsor two Humboldt penguins.
Begin with the source’s own compact description: “Chemnitz Linux Days” is event sequence. The dossier treats that line as a proposition to test through Chemnitz, Linux and Days, not as a finished interpretation.
Why this record matters
The phrase “event sequence” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
Chronology, provenance and viewpoint should be read together before a broad social or political interpretation is accepted. The source revision retrieved here is dated Feb 12, 2026. The linked authority identifier is Q1069580. Authority coordinates are 50.814, 12.930. 3 of 4 selected statements include explicit references; 2 carry qualifiers and 0 use preferred rank. The first chronological checks are 1999, 2000 and 2017.
Later summaries often reconcile disputed chronology or motive more neatly than the contemporary record permits. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Compare institutional narratives with records created by participants and affected communities. Dates and formal titles are useful anchors, but not substitutes for context.
- Event chronology
- Institutional context
- Locating named record creators
Contemporary correspondence, government or organizational records, oral histories and cited historical scholarship.
Three-step research path
- Establish the record: confirm the title “Chemnitz Linux Days”, its source revision and the description used here.
- Expand the search: follow Chemnitz Linux Days primary sources, Chemnitz Linux Days archive and Chemnitz research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Chemnitz Linux Days”?
- Who created the surviving record, and for what administrative purpose?
- Which voices are present, absent or mediated by the institution?
Search terms from this dossier
This entry incorporates text from “Chemnitz Linux Days” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.