Should Guix Get Its Own Tag on Lobsters?

The Lobsters community is currently debating whether Guix, the Scheme-based package manager and distribution, deserves its own dedicated tag separate from the existing Nix tag. The proposal, submitted by user untrusem, argues that while Guix began as a Nix fork, it has evolved significantly in recent years and should be treated as its own project.

The Case for Guix

The proposal highlights several developments that demonstrate Guix's maturation as an independent project. The community has seen the introduction of a new Rust build system, a move to Codeberg that brought in many new contributors, and the recent v1.5.0 release. Beyond technical achievements, the submitter emphasizes the strength of the Guix community itself, describing it as "small but very tightly-knit."

A key argument centers on the user experience for both Nix and Guix users. Currently, stories about Guix are tagged under Nix, which can be frustrating for users who want to filter content specific to their preferred system. As untrusem notes, "People who use nix might want to filter out guix stories that have got nothing to do with it and vice-versa for guix people."

The Counterarguments

Several community members have raised thoughtful objections to the proposal. Nemin, while personally supporting the idea as a Guix user, questions whether either project generates enough content to justify separate categories. They suggest a potential compromise: renaming the existing Nix tag to something more inclusive like "declarative" that would encompass both projects.

This suggestion sparked further discussion about terminology. Ploum points out that "declarative" might not be intuitive to users unfamiliar with the ecosystem, while alper raises concerns about whether such a tag would lead to mistagging. The conversation reveals the challenge of finding terminology that's both technically accurate and user-friendly.

Pushcx, a Lobsters sysop, provided valuable data to inform the discussion. Analysis of story tagging patterns shows that while Nix stories appear regularly (averaging about 10-15 per month), stories mentioning Guix within Nix-tagged content are relatively rare, appearing in only about 34 stories over several years. This data suggests that while Guix is growing, it hasn't yet reached a volume that clearly justifies separate categorization.

The Broader Context

The debate touches on deeper questions about how Lobsters organizes its content. Alper asks whether every project deserves its own tag, while kryptiskt notes that there aren't separate tags for other Linux distributions like Arch, Fedora, or Debian. This raises the question of whether Guix's functional programming approach and declarative configuration model make it fundamentally different from traditional distributions in a way that warrants special treatment.

Technical and Community Considerations

Beyond the immediate question of tagging, the discussion reveals interesting dynamics in the Nix/Guix ecosystem. Wink expresses surprise at any connection between the two projects beyond solving similar problems, suggesting that many users may not be aware of their relationship. Meanwhile, altano, a heavy Nix user, doesn't mind seeing Guix stories and finds them generally interesting, suggesting that the overlap between communities might be smaller than the proposal assumes.

Looking Forward

The proposal has sparked a nuanced conversation about community organization, technical categorization, and user experience. While there's no clear consensus yet, the discussion has been productive in clarifying the stakes and potential approaches.

Several paths forward emerge from the conversation:

1. Create a separate Guix tag - This would provide clear separation but might fragment the community unnecessarily given the current volume of content.

2. Rename the Nix tag to "declarative" - This could encompass both projects while acknowledging their shared approach to package management, though it risks being unclear to newcomers.

3. Maintain the status quo - Given the relatively low volume of Guix-specific content and the fact that many users don't mind seeing both, keeping things as they are might be the most pragmatic approach.

4. Create a broader tag - Suggestions like "immutable linux" or "functional package management" could provide a middle ground that acknowledges the relationship between these projects without creating unnecessary fragmentation.

The Way Forward

The discussion ultimately reflects the broader challenge of organizing technical communities as they evolve. Guix has clearly grown from its origins as a Nix fork into a distinct project with its own identity, community, and technical innovations. The question is whether that growth has reached a threshold that justifies separate categorization on Lobsters.

As the community continues to discuss, the outcome will likely depend on whether Guix can demonstrate not just technical maturity but also sufficient community engagement to justify the added complexity of another tag. The conversation serves as a reminder that tagging decisions aren't just about technical accuracy but about creating the best possible experience for a diverse community of users with varying interests and needs.

For now, the proposal remains open, and the community's thoughtful engagement suggests that whatever decision emerges will be well-considered and balanced against the needs of all Lobsters users, whether they prefer Nix, Guix, or simply want to stay informed about developments in declarative package management.