About documentation.

[Alain De Vos]

People helping writing FreeBSD Handbook.
They are not in center of scenes.
Not writing any "big kernel scheduling code".
But are doing a great job.
Big thanks to them.

And trust me sometimes i use NixOS. It will take them decades to come to same level as quality.

But writing documentation for FreeBSD, why ? It does not make you a code hero. But the importance can not be underenstimated.

 

[NapoleonWils0n]

And trust me sometimes i use NixOS. It will take them decades to come to same level as quality.

There is documentation for nixos ?
thats stretching it a bit

 

[Alain De Vos]

Yes there is , it is one percent. For other 99 percent the guideline is look at source code

 

[AlfredoLlaquet]

Respect for the writers. My homage:

Crumb 127: The Writer Wrote and Wrote: The writer wrote, and wrote and wrote. She wrote stories, recipes and novels. She wrote awake and sometimes not. She wrote in dreams and feverishly so. The writer wrote, and wrote and wrote. The writer wrote her life; and her life wrote and wrote.

 

[Alain De Vos]

I like this.

 

[AlfredoLlaquet]

When I still worked instead of trying to succeed as a writer, besides programming and system administration, I also did a ton of user-manual and documentation writing (I'm very versatile), so I know that it is demanding work that requires, among other things, great attention to detail.

 

[Alain De Vos]

Everone does what he is good at. I happen to be "second level support engineer".
This means you problem, i analyse. But I totally have no knowledge about sh-shell/C/C++. But if you installed wrong driver i'll try to help.
Thing is we all make are simple part.
Alfredo did you know "pkg update" failed once whole world.
I was the first to notice.
I did almost nothing but guided to "big developer behind the curtains'.
And he solved issue in 2 hours...

 

[AlfredoLlaquet]

Alfredo did you know "pkg update" failed once whole world.
I was the first to notice.
I did almost nothing but guided to "big developer behind the curtains'.
And he solved issue in 2 hours...

That is very impressive and a great story

 

[MG]

Is there any summary of still wanted FreeBSD documentation?

 

[AlfredoLlaquet]

Is there any summary of still wanted FreeBSD documentation?

According to ChatGPT:

---

Yes, but there is no single authoritative, curated “documentation wanted” list.

The closest things are:

• FreeBSD Bugzilla → Product: Documentation — probably the most practical backlog. It contains concrete outstanding work for the Handbook, manual pages, website, and related documentation.
  Open Documentation PRs in Bugzilla
  
• “Contributing to FreeBSD” → What Is Needed — the official overview. It specifically asks contributors to find outdated, ambiguous, poorly explained, or incorrect material in the Handbook and FAQ, and points newcomers toward Junior Jobs and the Ideas Page.
  Contributing to FreeBSD
  
• The Developers' Handbook and Architecture Handbook explicitly note that some sections do not yet exist and others need updating. Those books therefore represent substantial standing documentation work.
  FreeBSD Developers' Handbook

For someone looking for specific documentation that FreeBSD currently wants written, Bugzilla's Documentation product is the most useful starting point. The other pages describe broader needs, while Bugzilla provides discrete tasks that can be completed and submitted.

---

Edit: I love it when an LLM says "Yes," but in reality it should say "No." It happens a lot with ChatGPT.