[docs] Use .github/ISSUE_TEMPLATE.md from Bitcoin, with relevant tweaks
This commit is contained in:
parent
3ef8c14019
commit
0b7387a67c
|
@ -1,42 +1,21 @@
|
||||||
<!--- Remove text and sections that do not apply -->
|
<!-- This issue tracker is only for technical issues related to Bitcoin Private.
|
||||||
|
|
||||||
This issue tracker is only for technical issues related to btcpd.
|
General Bitcoin Private questions and/or support requests and are best directed to the [BTCP Support Website](https://support.btcprivate.org/). You can also email us at [core@btcprivate.org](mailto:core@btcprivate.org).
|
||||||
|
|
||||||
General Bitcoin Private questions and/or support requests and are best directed to the [BTCP Support Website](https://support.btcprivate.org/).
|
|
||||||
|
|
||||||
For reporting Zcash-specific security vulnerabilities or for sensitive discussions with their security team, please contact [security@z.cash](mailto:security@z.cash). You can use the [GPG key](https://z.cash/gpg-pubkeys/security.asc) (fingerprint: `AF85 0445 546C 18B7 86F9 2C62 88FB 8B86 D8B5 A68C`) to send an encrypted message. The key and fingerprint are duplicated on our [Public Keys page](https://z.cash/support/pubkeys.html).
|
For reporting Zcash-specific security vulnerabilities or for sensitive discussions with their security team, please contact [security@z.cash](mailto:security@z.cash). You can use the [GPG key](https://z.cash/gpg-pubkeys/security.asc) (fingerprint: `AF85 0445 546C 18B7 86F9 2C62 88FB 8B86 D8B5 A68C`) to send an encrypted message. The key and fingerprint are duplicated on our [Public Keys page](https://z.cash/support/pubkeys.html).
|
||||||
|
|
||||||
### Describe the issue
|
For reporting Bitcoin-specific security issues, please read the instructions at https://bitcoincore.org/en/contact/. -->
|
||||||
Please provide a general summary of the issue you're experiencing
|
|
||||||
|
|
||||||
### Can you reliably reproduce the issue?
|
<!-- Describe the issue -->
|
||||||
#### If so, please list the steps to reproduce below:
|
<!--- What behavior did you expect? -->
|
||||||
1.
|
|
||||||
2.
|
|
||||||
3.
|
|
||||||
|
|
||||||
### Expected behaviour
|
<!--- What was the actual behavior (provide screenshots if the issue is GUI-related)? -->
|
||||||
Tell us what should happen
|
|
||||||
|
|
||||||
### Actual behaviour + errors
|
<!--- How reliably can you reproduce the issue, what are the steps to do so? -->
|
||||||
Tell us what happens instead including any noticable error output (any messages displayed on-screen when e.g. a crash occurred)
|
|
||||||
|
|
||||||
### The version of Bitcoin Private you were using:
|
<!-- What version of Bitcoin Private are you using, where did you get it (website, self-compiled, etc)? -->
|
||||||
Run `btpcd --version` to find out
|
|
||||||
|
|
||||||
### Machine specs:
|
<!-- What type of machine are you observing the error on (OS/CPU and disk type)? -->
|
||||||
- OS name + version:
|
|
||||||
- CPU:
|
|
||||||
- RAM:
|
|
||||||
- Disk size:
|
|
||||||
- Disk Type (HD/SDD):
|
|
||||||
- Linux kernel version (uname -a):
|
|
||||||
- Compiler version (gcc -version):
|
|
||||||
|
|
||||||
### Any extra information that might be useful in the debugging process.
|
<!-- Any extra information that might be useful in the debugging process. -->
|
||||||
This includes the relevant contents of `~/.btcp/debug.log`. You can paste raw text, attach the file directly in the issue or link to the text via a pastebin type site.
|
<!--- This is normally the contents of a `debug.log` or `config.log` file. Raw text or a link to a pastebin type site are preferred. -->
|
||||||
Please also include any non-standard things you did during compilation (extra flags, dependency version changes etc.) if applicable.
|
|
||||||
|
|
||||||
### Do you have a back up of `~/.btcp` directory and/or take a VM snapshot?
|
|
||||||
- Backing up / making a copy of the `~/.btcp` directory might help make the problem reproducible. Please redact appropriately.
|
|
||||||
- Taking a VM snapshot is really helpful for interactively testing fixes
|
|
||||||
|
|
Loading…
Reference in New Issue