TKTuna Kılıç
All posts

Why I started a Turkish OSdev community

Operating system development is badly documented in English and almost undocumented in Turkish. Türk OSdev Topluluğu is my attempt to close some of that gap.

PublishedOSdev · Community · Turkish

When I started writing a kernel I did what everyone does. I opened the OSDev wiki, read the same three tutorials everyone reads, and then spent a lot of evenings stuck on things the tutorials had quietly skipped.

That is annoying in English. In Turkish it is worse, because most of the time there is simply nothing to find. Search for a Turkish explanation of how the GDT is set up, or what actually happens between the firmware handing off and your first C function running, and you get a couple of blog posts from years ago and a translated Wikipedia paragraph. Plenty of people here are curious about this stuff. They just hit a wall made of English jargon before they get to the interesting part.

So I started Türk OSdev Topluluğu. The tagline on the site is "işletim sistemi yazanlar burada buluşuyor", which is exactly what I wanted it to be: a place where the people writing this kind of code in Turkish are in the same room.

What is there

The main thing is the notes. Thirteen chapters so far, going from the toolchain and QEMU setup through architecture (x86-64, ARM64, RISC-V), the boot process (BIOS, UEFI, bootloaders), and assembly with NASM, registers and interrupts. They are written to be read in order, and they assume you know C but not that you have ever thought about what happens before main.

Everything lives on GitHub, which was a deliberate choice. Notes in a repo can be corrected by anyone who spots a mistake, and there have been mistakes. Open issues double as open topics: if a chapter has a gap, it goes in an issue, and whoever wants it opens a pull request.

How to join

Read something, and if a sentence is wrong or unclear, say so. That is genuinely the most useful contribution at this stage. After that, pick an open issue and write the missing part. You do not need to have finished an OS to help. Half the value of the notes comes from people who just learned a thing and still remember which part was confusing.

The site links to the GitHub organisation, and the issues list is the shortest path in.

Why bother

I am not going to pretend this fixes some enormous problem. It is a small community writing notes in a language that a limited number of people read.

But when I was starting out and trying to understand paging, a good Turkish explanation would have saved me a month. If the notes save someone else that month, the whole thing has paid for itself. And selfishly, writing a chapter is the fastest way I know to find out that I did not understand something as well as I thought.