remove bud and misleading onboarding docs #477
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This has been planned for some time. It seems necessary to do so now because after updating inputs to track NixOS 22.05 channels and releases, checks fail unexpectedly, with the traces leading back to `bud`. Disabling its modules allows checks to run successfully. Rather than figuring out what's going wrong with `bud`, it seems more appropriate to remove it as planned.
Many many people have complained about the misleading documentation. Rather than continuing the path of "we need to fix this", we can reduce the harmful effects of the inaccurate docs by removing them all together. Since much of the confusion in the "getting started" docs came from `bud`-specific instructions, and `bud` is being removed, removing the inaccurate docs also seems like it can be a kick towards replacing them. Also: - The NixOS manual is the canonical guide to installation. We don't need to repeat its instructions. - The numerous references to networking configuration don't have a place within Digga -- I'm assuming these are `bud`-specific things which are no longer relevant with `bud` gone.
montchr
changed the title
nrdxp
approved these changes
Jul 9, 2022
There was a problem hiding this comment.
LGTM. @blaggacao correct me if I'm wrong, but you probably don't have time maintain bud atm, so removing it is probably the right move at this point.
Pacman99
approved these changes
Jul 10, 2022
montchr
added a commit
that referenced
this pull request
Jul 10, 2022
support nixos 22.05 + remove bud and misleading onboarding docs (via #477)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This has been planned for some time.
It seems necessary to do so now because after updating inputs to track
NixOS 22.05 channels and releases, checks fail unexpectedly, with the
traces leading back to
bud. Disabling its modules allows checks torun successfully.
Rather than figuring out what's going wrong with
bud, it seems moreappropriate to remove it as planned.
Because this is closely related to updating Digga/Devos to support 22.05,
I've set #476 as a base branch.
Many many people have complained about the misleading documentation.
Rather than continuing the path of "we need to fix this", we can reduce
the harmful effects of the inaccurate docs by removing them all
together.
Since much of the confusion in the "getting started" docs came from
bud-specific instructions, andbudis being removed, removing theinaccurate docs also seems like it can be a kick towards replacing them.
Also:
to repeat its instructions.
within Digga -- I'm assuming these are
bud-specific things which areno longer relevant with
budgone.fixes #418