Doc update 2026 04 09

docs/_esnet/templates/layout.html

@@ -102,7 +102,7 @@
   <div class="container">
     <div class="row">
       <div class="col-md-1">
-        <a href="http://www.es.net/"><img src="_static/ESnet_Final_Logos_All_Blue_Circle_Stamp_RGB.png" alt="[ESnet]"></a>
+        <a href="https://www.es.net/"><img src="_static/ESnet_2025_001_2025_LogoShortName_RGB_Color.png" alt="[ESnet]"></a>
       </div>
       <div class="col-md-11">
         <p class="pull-right">

docs/_esnet/templates/navbar.html

@@ -34,7 +34,7 @@
                 <li><a href="{{ pathto(*link[1:]) }}">{{ link[0] }}</a></li>
               {%- endfor %}
             {% endif %}
-            <li><a href="{{ github_url }}"><img src="_static/icon-github.png" height="20" width="20"></a></li>
+            <li><a href="{{ github_url }}"><img src="_static/GitHub_Invertocat_Black.png" height="20" width="20"></a></li>
             {% block navbarextra %}
             {% endblock %}
             {% if theme_source_link_position == "nav" %}

docs/conf.py

@@ -112,7 +112,7 @@
 	"navbar_site_name": "Section",
     "navbar_links": [
         ("Index", "genindex"),
-        ("ESnet", "https://www.es.net", True),
+        ("<img src=\"_static/ESnet_2025_XX1B_2025_TILE_Orb_RGB_Color.png\" height=20 width=20>", "https://www.es.net", True),
     ],
 }
 
@@ -176,7 +176,7 @@
 #html_split_index = False
 
 # If true, links to the reST sources are added to the pages.
-#html_show_sourcelink = True
+html_show_sourcelink = False
 
 # If true, "Created using Sphinx" is shown in the HTML footer. Default is True.
 #html_show_sphinx = True

docs/dev.rst

@@ -3,7 +3,7 @@ iperf3 Development
 
 The iperf3 project is hosted on GitHub at:
 
-http://github.com/esnet/iperf
+https://github.com/esnet/iperf
 
 This site includes the source code repository, issue tracker, and
 discussion forums.
@@ -14,7 +14,7 @@ Mailing Lists
 The developer list for iperf3 is:  iperf-dev@googlegroups.com.
 Information on joining the mailing list can be found at:
 
-http://groups.google.com/group/iperf-dev
+https://groups.google.com/group/iperf-dev
 
 Project Constituencies
 ----------------------
@@ -146,7 +146,7 @@ Versioning
 ----------
 
 iperf3 version numbers use (roughly) a `Semantic Versioning
-<http://semver.org/>`_ scheme, in which version numbers consist of
+<https://semver.org/>`_ scheme, in which version numbers consist of
 three parts:  *MAJOR.MINOR.PATCH*
 
 The developers increment the:
@@ -223,16 +223,14 @@ Release Engineering Checklist
 9. Merge pull request to `master` or other appropriate integration
    branch.
 
-10. Create tag and tarfile::
+10. Create tag and tarfile.
+    The result will be release artifacts that should be used for
+    pre-testing. One will be a compressed tarball
+    (e.g. ``iperf-3.20.tar.gz``) and the other will contain SHA256
+    checksum (e.g. ``iperf-3.20.tar.gz.sha256``)::
 
-    # Assuming that $VERSION is the version number to be released...
-    ./make_release tag $VERSION # this creates a tag in the local repo
-    ./make_release tar $VERSION # create tarball and compute SHA256 hash
-
-   The result will be release artifacts that should be used for
-   pre-testing. One will be a compressed tarball
-   (e.g. ``iperf-3.20.tar.gz``) and the other will contain SHA256
-   checksum (e.g. ``iperf-3.20.tar.gz.sha256``)
+    ./make_release tag 3.20 # this creates a tag in the local repo
+    ./make_release tar 3.20 # create tarball and compute SHA256 hash
 
 6. Stage the tarball (and a file containing the SHA256 hash) to the
    download site.  Currently this is located on ``downloads.es.net``

docs/faq.rst

@@ -12,7 +12,7 @@ What is the history of iperf3, and what is the difference between iperf2 and ipe
   base. For this reason, it was decided to make the tool single
   threaded, and not worry about backwards compatibility with
   iperf2. Many of the feature requests for iperf3 came from the
-  perfSONAR project (http://www.perfsonar.net).
+  perfSONAR project (https://www.perfsonar.net).
 
   Then in 2014, Bob (Robert) McMahon from Broadcom restarted
   development of iperf2 (See
@@ -262,7 +262,7 @@ A file sent using the ``-F`` option got corrupted...what happened?
 
 I have a question regarding iperf3...what's the best way to get help?
   Searching on the Internet is a good first step.
-  http://stackoverflow.com/ has a number of iperf3-related questions
+  https://stackoverflow.com/ has a number of iperf3-related questions
   and answers, but a simple query into your favorite search engine can
   also yield some results.
 

docs/index.rst

@@ -3,6 +3,8 @@
    You can adapt this file completely to your liking, but it should at least
    contain the root `toctree` directive.
 
+.. image:: _static/iperf3-logos-0410_6.png
+
 iperf3
 ======
 
@@ -27,8 +29,8 @@ and macOS.  At this time, these are the only officially
 supported platforms, however there have been some reports of success
 with OpenBSD, Android, and other Linux distributions.
 
-iperf3 is principally developed by `ESnet <http://www.es.net/>`_ /
-`Lawrence Berkeley National Laboratory <http://www.lbl.gov/>`_.  It
+iperf3 is principally developed by `ESnet <https://www.es.net/>`_ /
+`Lawrence Berkeley National Laboratory <https://www.lbl.gov/>`_.  It
 is released under a three-clause BSD license.
 
 iperf2 is no longer being developed by its original maintainers.