[Bug] Convert proposals to issues or delete them #781

Closed
opened 2025-12-29 02:23:57 +01:00 by adam · 2 comments
Owner

Originally created by @nblock on GitHub (Sep 4, 2024).

Is this a support request?

  • This is not a support request

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

The documentation contains two proposals docs/proposals/001-acls.md and docs/proposals/002-better-routing.md. Both are from early 2022 and those should not be part of the user documentation as they are not actionable for users.

Expected Behavior

Convert them to issues, probably feature requests. Or, in case they are no longer valid: delete them.

Steps To Reproduce

not relevant

Environment

not relevant

Runtime environment

  • Headscale is behind a (reverse) proxy
  • Headscale runs in a container

Anything else?

No response

Originally created by @nblock on GitHub (Sep 4, 2024). ### Is this a support request? - [X] This is not a support request ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current Behavior The documentation contains two proposals `docs/proposals/001-acls.md` and `docs/proposals/002-better-routing.md`. Both are from early 2022 and those should not be part of the user documentation as they are not actionable for users. ### Expected Behavior Convert them to issues, probably feature requests. Or, in case they are no longer valid: delete them. ### Steps To Reproduce not relevant ### Environment ```markdown not relevant ``` ### Runtime environment - [ ] Headscale is behind a (reverse) proxy - [ ] Headscale runs in a container ### Anything else? _No response_
adam added the bug label 2025-12-29 02:23:57 +01:00
adam closed this issue 2025-12-29 02:23:57 +01:00
Author
Owner

@kradalby commented on GitHub (Sep 5, 2024):

I'm ok with this, they are implemented I think, or likely not relevant, and we can find them in git. The proposals didnt work out the way we envisioned and it might be equally useful to do issues, or google docs in the future.

Happy for you to raise a PR to delete them and the links in the doc page.

@kradalby commented on GitHub (Sep 5, 2024): I'm ok with this, they are implemented I think, or likely not relevant, and we can find them in git. The proposals didnt work out the way we envisioned and it might be equally useful to do issues, or google docs in the future. Happy for you to raise a PR to delete them and the links in the doc page.
Author
Owner

@nblock commented on GitHub (Sep 5, 2024):

I'm ok with this, they are implemented I think, or likely not relevant, and we can find them in git. The proposals didnt work out the way we envisioned and it might be equally useful to do issues, or google docs in the future.

Happy for you to raise a PR to delete them and the links in the doc page.

OK, thx for the feedback! Will open a PR soonish.

@nblock commented on GitHub (Sep 5, 2024): > I'm ok with this, they are implemented I think, or likely not relevant, and we can find them in git. The proposals didnt work out the way we envisioned and it might be equally useful to do issues, or google docs in the future. > > Happy for you to raise a PR to delete them and the links in the doc page. OK, thx for the feedback! Will open a PR soonish.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#781