Enhancing FreeBSD's Jargon for New Users

vimanuelt

FreeBSD's terminology can be daunting for newcomers. While experienced users adapt easily, clearer language would make FreeBSD more approachable without sacrificing technical precision. Here are a few proposals for name changes:

Ports → Build Kit
Why: Clear and highlights its role as a software build toolkit. Installing from a build kit (or source kit) sounds relatively better than saying I'm installing from ports.
Jail → System Isolation (isltn)
Why: Modern and aligns with containerization concepts. Installing system isolation makes more sense.
bhyve → FreeBSD Hypervisor (hyprv)
Why: Instantly recognizable as a virtualization tool.
RELEASE → Production
STABLE → Maintenance
CURRENT → Development
Why: Simple, familiar terms that clarify each branch’s purpose.

While it may seem like a bold idea, modernizing terminology in FreeBSD can help lower barriers for new users and enhance clarity.

brianthehughes

vimanuelt

I like all the suggestions.

When it comes to relabelling Ports... I don't know if Build Kit, Source Kit, Build Toolkit is much better since you describe it three ways indicating some room to align on a more universal term. I asked the oracle (ChatGPT) and it spit out... (among 13 other possibilities...)

Source Trees / Source Repositories - which did resonate a bit for me. I like the simplicity and somewhat encompassing idea of "Sources"

It also spit out Build Kits / Build Systems - so I see where you're coming from there. My concern is that it would end up being abbreviated and implemented as 'Kits" /kits (because that's what humans do...) and I think that is no better than ports.

But Sources... is singular/plural and a single word directory path.

I feel like it's important to consider the relationship with Packages in a graceful way and Sources/Source Kit does that best, in my opinion.

3. Source Trees / Source Repositories

Definition: This refers to the entire directory structure containing the source code and often build instructions for software projects.
Examples: The Linux kernel source tree, a source tree for a software project like Apache or Nginx.
Context: This term is often used in larger projects, particularly when dealing with a full source code repository, such as a Git repository containing source code files and build configurations.

vimanuelt

brianthehughes Yes, and "Source Collection" comes to mind.

Robin

In Salix they have a tool that kinda-sorta does that. They called it Sourcery. Very cool name for a very cool Slackware build-it-on-the-fly script.

grahamperrin

I do like bold ideas, however I'm fairly certain that some of what's proposed will never change.
Generally: it's important to raise awareness of, and improve, the glossary.
https://docs.freebsd.org/en/books/handbook/glossary/ | https://docs.freebsd.org/en/books/handbook/glossary/
273545 – FreeBSD Handbook: improve the glossary

vimanuelt

grahamperrin I see your point. I previously wrote an article on X.com titled "FreeBSD’s Nostalgia Problem and What It Means for GhostBSD," discussing FreeBSD’s reluctance to embrace change.

grahamperrin

I think, we need a separate topic for change management etc. (I have something drafted, it's way off-topic from jargon for new users) …

vimanuelt

An open-source project could benefit from a Behavioral Computing section to examine resistance to change and develop strategies for fostering adaptability.