This commit is contained in:
Frank Denis 2021-03-27 01:19:01 +01:00
parent 6430ae942c
commit 1e3f03ab0c
5 changed files with 16 additions and 121 deletions

View File

@ -9,19 +9,21 @@ assignees: ''
## Please read the context below before submitting a bug report
This is not a place to ask for support.
The issue tracker is reserved to tracking bugs, reproducible in the context described in the
"Context" section.
Installation and configuration issues are not bugs, but individual assistance request.
In order to ask for help, please use the [discussions](https://github.com/DNSCrypt/dnscrypt-proxy/discussions/categories/q-a) section instead.
<!--
Context: the LATEST version of `dnscrypt-proxy` (precompiled binaries downloaded from this
repository) is correctly installed and configured on your system, but something doesn't
seem to produce the expected result.
This is the right place to report it! Thanks for finding and reporting what may indeed be a bug!
If the bug is not trivial to reproduce on any platform, please include ALL the steps required
to reliably duplicate it, on a vanilla, generic install of macOS, Windows, OpenBSD or Ubuntu Linux
system, in their most current version.
-->
## Output of the following commands:

View File

@ -1,22 +0,0 @@
---
name: "⛹🏼 Contributions"
about: Contribute to the project
title: ''
labels: ''
assignees: ''
---
## Subject
* [ ] I'd like to contribute to the project (code, documentation, website, advocacy, integration, ...)
* [ ] I want to run my own DNSCrypt and/or DoH server
* [ ] I'd like to have my existing server added to a public list of encrypted DNS servers
* [ ] I'd like to announce a new application/website/article related to the project
* [ ] I have questions about the DNSCrypt or Anonymized DNSCrypt protocols
* [ ] I am a MacOS developer and I'd like to contribute a GUI for dnscrypt-proxy
* [ ] I am an Android developer and I'd like to contribute an Android app
* [ ] I am a technical writer and I'd like to help write an IETF Internet Draft for the DNSCrypt protocol
* [ ] Other
## Description

View File

@ -1,12 +0,0 @@
---
name: "🧚🏼‍♂️ Protocol"
about: Questions about the DNSCrypt protocol (not dnscrypt-proxy) and its implementations
title: ''
labels: ''
assignees: ''
---
<!--
Questions about the protocol itself, its implementations and how to operate a server.
-->

View File

@ -1,37 +1,22 @@
---
name: "\U0001F389 Suggestions"
about: Suggest an improvement idea for this project
name: "🙋🏽 Planned changes"
about: List of planned changes
title: ''
labels: ''
assignees: ''
---
## Describe the improvement you are thinking of
<!-- A clear and concise description of what you want to happen. -->
The starting point should be a discussion.
https://github.com/DNSCrypt/dnscrypt-proxy/discussions/
Possible bugs may be raised as a "Potential issue" discussion, suggestions may be raised as an "Ideas" discussion.
## Alternatives you've considered
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
We can then determine if the discussion needs to be escalated into a "planned change" or not.
This will help us ensure that the issue tracker properly reflects ongoing or needed work on the project.
---
## Who will that feature be useful to?
<!-- Is it solving a common problem, or is it an improvement that all current users will benefit from? -->
## What have you done already?
<!-- If you already built a prototype or a complete implementation of that feature, where is it possible to see it? -->
## What are you going to contribute?
<!-- Besides testing volunteering work made by other people, what are you going to contribute in order to help have that feature implemented, tested and documented? -->
## Additional context
<!-- Add any other context about the feature request here. -->
- [ ] Initially raised as discussion #...

View File

@ -1,58 +0,0 @@
---
name: "🙋🏽 Support"
about: Free customer service line
title: ''
labels: ''
assignees: ''
---
<!--
Hi!
Please understand that this project is maintained by volunteers, and that answering support
tickets to help with specific, personal issues is time consuming, mentally exhausting, and
is time not spend in improving the software itself.
Saying hi, thank you and clearly describing what problem you are trying to solve (not
what you tried and didn't work) would be both polite and fantastic.
In order for the answer to be easy to find for other people hitting the same thing,
please write a short summary in the title ("problem" and "doesn't work" are very
depressing to read, and don't make a description unique - show that you can do better!)
Make sure that you are using the last version (downloaded from this repository or installed
via Homebrew), and that you read the documentation. If you did read the documentation, copy
and paste the code you saw to this ticket in order to give it a high priority.
If you are not using the default configuration (Fine! This is a configuration after all),
try the default configuration, changing only the listening IP addresses if necessary.
Many reported issues were actually due to too many changes having been made at the same
time, making it difficult to pinpoint which one didn't work as expected. So, start with
a standard configuration and do small, incremental changes.
The only supported way to install the service is `dnscrypt-proxy -service install`.
Prior to that, run `dnscrypt-proxy` interactively and check for any errors.
You already saw `dnscrypt-proxy -resolve` in the documentation. If you are experiencing
resolution issues, use this command to resolve DNS queries for diagnostics, not a web
browser. If responses are printed just fine while domain names don't resolve in the
web browser, the actual issue is likely to be located in 3rd party software such as
dnsmasq.
Maintainers may not use your operating system and hardware. In order to respond to
questions on environments they don't know about, the best they can do is do a Google
search, as an attempt to solve a problem you have, but that they don't have. You are
the one who knows your own environment the best. So, take some time trying to solve
issues on your own first; this is by far the best way to understand how the whole
thing works. Answering our own question right after having formulated it happens
all the time!
Finally, if the issue is solved, and this is something that wouldn't have happened if
it had been documented, feel free to proudly improve the documentation (it is a wiki).
Thanks for reading all this, and have a wonderful day!
(you can now delete all this to start writing a beautiful blank page)
-->