summaryrefslogtreecommitdiff
path: root/docs/contributing/md-issues-features.md
diff options
context:
space:
mode:
authorDaniil Baturin <daniil@vyos.io>2026-05-06 14:09:07 +0100
committerGitHub <noreply@github.com>2026-05-06 14:09:07 +0100
commite066bb43eab070c58043f69efe87191b354b01e5 (patch)
treea390c8fddb08a163feef6710818c10ffdc553733 /docs/contributing/md-issues-features.md
parent22e34ce5aee24d2fd11f8205522ab7ecdb3c4c5e (diff)
downloadvyos-documentation-e066bb43eab070c58043f69efe87191b354b01e5.tar.gz
vyos-documentation-e066bb43eab070c58043f69efe87191b354b01e5.zip
Revert "Add incremental RST-to-MyST swap mechanism (sagitta) (#1868)" (#1894)
This reverts commit 22e34ce5aee24d2fd11f8205522ab7ecdb3c4c5e.
Diffstat (limited to 'docs/contributing/md-issues-features.md')
-rw-r--r--docs/contributing/md-issues-features.md60
1 files changed, 0 insertions, 60 deletions
diff --git a/docs/contributing/md-issues-features.md b/docs/contributing/md-issues-features.md
deleted file mode 100644
index c481fec5..00000000
--- a/docs/contributing/md-issues-features.md
+++ /dev/null
@@ -1,60 +0,0 @@
-# Issues/Feature requests
-
-## Bug Report/Issue
-
-Issues or bugs are found in any software project. VyOS is not an exception.
-
-All issues should be reported to the developers. This lets the developers know
-what is not working properly. Without this sort of feedback every developer
-will believe that everything is working correctly.
-
-### I have found a bug, what should I do?
-
-When you believe you have found a bug, it is always a good idea to verify the
-issue prior to opening a bug request.
-
-- Consult the [documentation](https://docs.vyos.io) to ensure that you have configured your system
- correctly
-- Get community support via [Slack](https://slack.vyos.io) or our [Forum](https://forum.vyos.io)
-
-### Ensure the problem is reproducible
-
-When you are able to verify that it is actually a bug, spend some time to
-document how to reproduce the issue. This documentation can be invaluable.
-
-When you wish to have a developer fix a bug that you found, helping them
-reproduce the issue is beneficial to everyone. Be sure to include information
-about the hardware you are using, commands that you were running, any other
-activities that you may have been doing at the time. This additional
-information can be very useful.
-
-- What were you attempting to achieve?
-- What was the configuration prior to the change?
-- What commands did you use? Use e.g. `run show configuration commands`
-
-### Include output
-
-The output you get when you find a bug can provide lots of information. If you
-get an error message on the screen, copy it exactly. Having the exact message
-can provide detail that the developers can use. Like wise if you have any log
-messages that also are from the time of the issue, include those. They may
-also contain information that is helpful for the development team.
-
-### Report a Bug
-
-In order to open up a bug-report/feature request you need to create yourself
-an account on VyOS [Phabricator](). On the left side of the specific project (VyOS
-1.2 or VyOS 1.3) you will find quick-links for opening a bug-report/feature
-request.
-
-- Provide as much information as you can
-- Which version of VyOS are you using? `run show version`
-- How can we reproduce this Bug?
-
-## Feature Request
-
-You have an idea of how to make VyOS better or you are in need of a specific
-feature which all users of VyOS would benefit from? To send a feature request
-please search [Phabricator]() if there is already a request pending. You can
-enhance it or if you don't find one, create a new one by use the quick link in
-the left side under the specific project.