Proposal: Add `Guix` tag
22 points by untrusem
22 points by untrusem
It is viewed as just a nix fork with scheme on top of in many communities I am in, while yes it might be started off as that but it has grown significantly in the recent years that it should be treated as its own project.
I have been just in guix community for like year and so but I have seen very good changes, some of them would
But what I like most about the guix project is the people there, It is small but very tightly-knit community. So I believe guix deserve its own tag now.
ps - I am adding more text that follows the guidelines, thanks @gerikson for pointing this out
Name: "guix"
Description: "A transactional scheme based package manager and distribution"
Category: package management, declarative configuration
Similar tag: nix
Recent Stories:
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 increased complexity for submitter and mods is justified by the fact that this tag will set a clear distinction between the two and this should make it easy for both submitter and mods as tagging gnu guix 1.5.0 release as nix tag doesn't seem right.
As a Guix user, obviously I'd support this proposal.
But as a Lobsters user, I'm not sure either Nix or Guix has enough posts to get two separate categories. So it might be more worth keeping the single category and just renaming it to be something less Nix-specific ("declarative" perhaps?)
I agree. The nix tag is already defined somewhat inclusively as "package manager, distribution, and related systems like guix". I'm not sure if there is a precedent for renaming tags like that, but these sort of declarative/reproducible build tools should fit together in one tag IMO.
I disagree because while I understand "nix" and "guix", I would never guess that "declarative" means both of them.
Regarding the concern that a tag named 'declarative' would lead to mistagging: typing 'humor' into the tag input during story submission already suggests the 'satire' tag, so a 'declarative' tag with both nix and guix mentioned in its tag description would function the same way.
I think it could make sense to generalize nix into "packagemanagement"?
I see there's also not a specific tag for build systems?
I see your logic, but personally I disagree.
There's quite a bit of difference between, say, npm, apt, bazel, and nix/guix, even though they're all package management tools. The reason why I suggested declarative is because it's a well-defined subset of package management, and even if the details differ, the overarching idea is the same ("state is captured in a file" and "you tell the system 'what', not 'how'").
Nix being under OS does not really help here.
So "declarative" is short for "declarative package management" and the non-declarative ones wouldn't get their own tag?
From the About page guidelines for proposing new tags
To propose a tag, post a meta thread with the name and description. Explain the scope, list existing stories that should have been tagged, make a case for why people would want to specifically filter it out, and justify the increased complexity for submitters and mods.
It feels wrong to submit Guix articles under the nix tag. I would be in favor of either a guix tag or a new tag that encompasses functional package managers generally.
There doesn't seem to be any confusion and I think the two projects still interoperate, right? Guix and Lix seem to be healthy projects, but overall the family is not so busy or divided that this categorization seems worthwhile.
The nix tag sees steady use:
MariaDB [lobsters]> select date_format(stories.created_at, "%Y-%m"), count(*) from stories join taggings on s
tories.id = taggings.story_id join tags on taggings.tag_id = tags.id where tags.tag = 'nix' group by 1 order
by stories.created_at asc;
+------------------------------------------+----------+
| date_format(stories.created_at, "%Y-%m") | count(*) |
+------------------------------------------+----------+
| 2021-11 | 5 |
| 2021-12 | 7 |
| 2022-01 | 6 |
| 2022-02 | 6 |
| 2022-03 | 4 |
| 2022-04 | 7 |
| 2022-05 | 15 |
| 2022-06 | 8 |
| 2022-07 | 8 |
| 2022-08 | 10 |
| 2022-09 | 15 |
| 2022-10 | 11 |
| 2022-11 | 13 |
| 2022-12 | 16 |
| 2023-01 | 10 |
| 2023-02 | 10 |
| 2023-03 | 23 |
| 2023-04 | 15 |
| 2023-05 | 6 |
| 2023-06 | 16 |
| 2023-07 | 8 |
| 2023-08 | 14 |
| 2023-09 | 13 |
| 2023-10 | 13 |
| 2023-11 | 22 |
| 2023-12 | 12 |
| 2024-01 | 18 |
| 2024-02 | 12 |
| 2024-03 | 24 |
| 2024-04 | 17 |
| 2024-05 | 11 |
| 2024-06 | 12 |
| 2024-07 | 14 |
| 2024-08 | 15 |
| 2024-09 | 10 |
| 2024-10 | 10 |
| 2024-11 | 10 |
| 2024-12 | 8 |
| 2025-01 | 12 |
| 2025-02 | 9 |
| 2025-03 | 15 |
| 2025-04 | 8 |
| 2025-05 | 11 |
| 2025-06 | 11 |
| 2025-07 | 14 |
| 2025-08 | 13 |
| 2025-09 | 11 |
| 2025-10 | 18 |
| 2025-11 | 8 |
| 2025-12 | 17 |
| 2026-01 | 9 |
| 2026-02 | 15 |
| 2026-03 | 1 |
+------------------------------------------+----------+
53 rows in set (0.009 sec)
And then checking for stories that mention "guix" in the title, description, or bodies (we get this from links via diffbot almost all of the time), which will be a bit of an overcount because it'll include anything that mentions it in passing once:
MariaDB [lobsters]> select date_format(stories.created_at, "%Y-%m"), count(*) from stories join taggings on s
tories.id = taggings.story_id join tags on taggings.tag_id = tags.id join story_texts st on stories.id = st.i
d where tags.tag = 'nix' and (st.title like '%guix%' or st.description like '%guix%' or st.body like '%guix%'
) group by 1 order by stories.created_at asc;
+------------------------------------------+----------+
| date_format(stories.created_at, "%Y-%m") | count(*) |
+------------------------------------------+----------+
| 2021-12 | 3 |
| 2022-01 | 1 |
| 2022-04 | 1 |
| 2022-05 | 2 |
| 2022-06 | 1 |
| 2022-08 | 1 |
| 2022-09 | 2 |
| 2022-12 | 3 |
| 2023-01 | 2 |
| 2023-02 | 1 |
| 2023-04 | 1 |
| 2023-06 | 2 |
| 2023-08 | 1 |
| 2023-10 | 1 |
| 2023-11 | 3 |
| 2024-02 | 1 |
| 2024-03 | 1 |
| 2024-04 | 1 |
| 2024-06 | 1 |
| 2024-10 | 3 |
| 2024-11 | 2 |
| 2025-01 | 3 |
| 2025-02 | 1 |
| 2025-03 | 1 |
| 2025-05 | 1 |
| 2025-06 | 1 |
| 2025-07 | 2 |
| 2025-08 | 1 |
| 2025-10 | 1 |
| 2025-11 | 1 |
| 2025-12 | 2 |
| 2026-01 | 2 |
| 2026-02 | 6 |
| 2026-03 | 1 |
+------------------------------------------+----------+
34 rows in set (0.078 sec)
as its own project
Should every project get its own tag?
There the precedence of "systemd"...
I think that one mostly exists because systemd was so contentious for its first few years, and the heavily BSD early users of Lobsters were especially uninterested in it. We could probably retire it. Maybe there's others worth retiring? Could I talk you into the project, maybe sketch out a rough activity level to justify a tag and we'll review annually?
Thanks for sharing the description of what a tag proposal should have elsewhere in this thread.
I was not even aware there was any connection between nix and guix except "roughly tries to solve some of the same problems". (so yes)
There are no tags for Linux distros other than nix, why should there be a guix tag when there aren't arch, fedora, debian etc tags? It seems to me that the tags aren't granular in a way where it makes sense that guix is one.