d/iperf3-tls
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update templates to point users at GitHub Discussions for support.

Browse Source
This commit is contained in:
Bruce A. Mah 2021-11-15 16:39:56 -08:00
parent d424be34a9
commit 9e2d79d262
No known key found for this signature in database
GPG Key ID: 4984910A8CAAEE8A
2 changed files with 17 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
.github/CONTRIBUTING.md vendored
View File

@ -14,19 +14,20 @@ FreeBSD, and macOS. Support may be provided on a best-effort basis to
other UNIX-like platforms. We cannot provide support for building other UNIX-like platforms. We cannot provide support for building
and/or running iperf3 on Windows, iOS, or Android. and/or running iperf3 on Windows, iOS, or Android.
Before asking for help, please use your favorite search engine or Before asking for help, please check with your favorite search engine
questions site (such as Stack Overflow) to see if your question might or the
have been asked (and maybe even answered) before. [iperf3 Discussions site on GitHub](http://github.com/esnet/iperf/discussions)
https://fasterdata.es.net/ has some information on the use of various to see if your question might have been asked (and maybe even
bandwidth measurement tools, including iperf3. The iperf3 answered) before. https://fasterdata.es.net/ has some information on
documentation Web site at http://software.es.net/iperf/ contains the use of various bandwidth measurement tools, including iperf3. The
various bits of helpful information, including a list of iperf3 documentation Web site at http://software.es.net/iperf/
contains various bits of helpful information, including a list of
[frequently-asked questions](http://software.es.net/iperf/faq.html). [frequently-asked questions](http://software.es.net/iperf/faq.html).
We specifically discourage the use of the issue tracker on the iperf3 We specifically discourage the use of the issue tracker on the iperf3
GitHub project page for asking questions. Questions posted in the GitHub project page for asking questions. Questions posted in the
form of issues may go unanswered. Please use a questions site form of issues may go unanswered. Please use the
such as [Stack Overflow](http://www.stackoverflow.com) [iperf3 Discussions site on GitHub](http://github.com/esnet/iperf/discussions)
to ask questions of the community or to ask questions of the community or
alternatively use the iperf3 mailing list at alternatively use the iperf3 mailing list at
iperf-dev@googlegroups.com (posting requires joining the list). iperf-dev@googlegroups.com (posting requires joining the list).

15
.github/ISSUE_TEMPLATE.md vendored
View File

@ -1,9 +1,10 @@
_NOTE: The iperf3 issue tracker is for registering bugs, enhancement _NOTE: The iperf3 issue tracker is for registering bugs, enhancement
requests, or submissions of code. It is not a means for asking requests, or submissions of code. It is not a means for asking
questions about building or using iperf3. Those are best directed questions about building or using iperf3. Those are best directed
towards the iperf3 mailing list at iperf-dev@googlegroups.com or towards the Discussions section for this project at
question sites such as Stack Overflow https://github.com/esnet/iperf/discussions
(http://www.stackoverflow.com/). A list of frequently-asked questions or to the iperf3 mailing list at iperf-dev@googlegroups.com.
A list of frequently-asked questions
regarding iperf3 can be found at http://software.es.net/iperf/faq.html._ regarding iperf3 can be found at http://software.es.net/iperf/faq.html._
# Context # Context
@ -23,7 +24,9 @@ iperf3 on Windows, iOS, or Android._
libraries, cross-compiling, etc.): libraries, cross-compiling, etc.):
_Please fill out one of the "Bug Report" or "Enhancement Request" _Please fill out one of the "Bug Report" or "Enhancement Request"
sections, as appropriate._ sections, as appropriate. Note that submissions of bug fixes, new
features, etc. should be done as a pull request at
https://github.com/esnet/iperf/pulls_
# Bug Report # Bug Report
@ -35,8 +38,6 @@ sections, as appropriate._
* Possible Solution * Possible Solution
_Please submit patches or code changes as a pull request._
# Enhancement Request # Enhancement Request
* Current behavior * Current behavior
@ -45,5 +46,3 @@ _Please submit patches or code changes as a pull request._
* Implementation notes * Implementation notes
_If submitting a proposed implementation of an enhancement request,
please use the pull request mechanism._