Update references to Discuss pages

These are no longer under /help
imagej · May 27, 2021 · e0234f3 · e0234f3
1 parent c7d5117
commit e0234f3
Show file tree

Hide file tree

Showing 52 changed files with 68 additions and 68 deletions.
diff --git a/_includes/layout/menu b/_includes/layout/menu
@@ -203,10 +203,10 @@
             {% include menu/section-end %} <!-- Contribute/Editing the Wiki -->
           {% include menu/section-end %} <!-- Contribute -->
 
-          {% include menu/section title="Discuss" link="/help" %}
+          {% include menu/section title="Discuss" link="/discuss" %}
             <li><a href="/discuss/bugs">Reporting Issues</a></li>
-            <li><a href="/help/mailing-lists">Mailing Lists</a></li>
-            <li><a href="/help/chat">Chat</a></li>
+            <li><a href="/discuss/mailing-lists">Mailing Lists</a></li>
+            <li><a href="/discuss/chat">Chat</a></li>
           {% include menu/section-end %} <!-- Discuss -->
 
           {% include menu/section title="Explore" %}

diff --git a/_includes/warning/outdated b/_includes/warning/outdated
@@ -1,4 +1,4 @@
-{% include notice icon="warning" content="This section is out of date, potentially misleading or invalid. Be careful with any instructions here. When in doubt, [ask for help from the community](/help)." %}
+{% include notice icon="warning" content="This section is out of date, potentially misleading or invalid. Be careful with any instructions here. When in doubt, [ask for help from the community](/discuss)." %}
 
 {%- comment -%}
 # vi:syntax=liquid

diff --git a/_includes/warning/unmaintained b/_includes/warning/unmaintained
@@ -1,4 +1,4 @@
-{% include notice icon="warning" content="This page describes a [plugin](/plugins) which is **_UNMAINTAINED_**! While the plugin and documentation remain available for use, no one is pledged to fix bugs or respond to support questions about it. You can try [asking for help from the community](/help), but your mileage may vary." %}
+{% include notice icon="warning" content="This page describes a [plugin](/plugins) which is **_UNMAINTAINED_**! While the plugin and documentation remain available for use, no one is pledged to fix bugs or respond to support questions about it. You can try [asking for help from the community](/discuss), but your mileage may vary." %}
 
 {%- comment -%}
 # vi:syntax=liquid

diff --git a/_pages/Installing_3rd_party_plugins.md b/_pages/Installing_3rd_party_plugins.md
@@ -37,7 +37,7 @@ It will ask you for the file name of the plugin, and install the given file.
 
 ## For developers
 
-{% include notice icon="warning" content='This section is out of date, potentially misleading or invalid. Be careful with any instructions here. When in doubt,  [ask for help from the community](/help).' %}
+{% include notice icon="warning" content='This section is out of date, potentially misleading or invalid. Be careful with any instructions here. When in doubt,  [ask for help from the community](/discuss).' %}
 
 Please try to avoid closed-source plugins.
 

diff --git a/_pages/contribute/governance.md b/_pages/contribute/governance.md
@@ -23,7 +23,7 @@ Because [open source](Open_source) software (OSS) is highly collaborative, it is
 The most common roles in OSS are:
 
 -   **Founders** are the people who originally launched the project.
--   **Leads** are responsible for making final decisions. In the [open source](Open_source) world these people are often referred to as [benevolent dictators](http://catb.org/~esr/writings/homesteading/homesteading/ar01s16.html). Changes with a serious impact on the community are typically [discussed on open channels](/help) first.
+-   **Leads** are responsible for making final decisions. In the [open source](Open_source) world these people are often referred to as [benevolent dictators](http://catb.org/~esr/writings/homesteading/homesteading/ar01s16.html). Changes with a serious impact on the community are typically [discussed on open channels](/discuss) first.
 -   **Maintainers** keep the project functional, fix bugs and make releases. They often make day to day decisions, and are typically involved in discussion with the project lead(s) regarding major decisions, although the lead has final decision-making authority.
 -   **Developers** are people who work on the project significantly or often. Typically they have direct push access to the source code. In some cases they make day to day decisions, depending on their experience and comfort level with the project.
 -   **Contributors** are people who help with the project either currently or in the past. They may participate occasionally or sporadically, and are typically not involved in project decision making.
@@ -39,7 +39,7 @@ Projects in the [SciJava component collection](/develop/architecture) define eac
 | Developer   | Adds new features or enhancements. Can be assigned to address feature requests.                                                    |
 | Debugger    | Fixes [bugs](//develop/project-management#issue-tracking). Can be assigned open [issues](//develop/project-management#issue-tracking) to solve.                                        |
 | Reviewer    | Reviews [patch submissions](/contribute).                                                                              |
-| Support     | Responds to [community questions](/help) and [issue reports](//develop/project-management#issue-tracking). Keeps the issue tracker organized. |
+| Support     | Responds to [community questions](/discuss) and [issue reports](//develop/project-management#issue-tracking). Keeps the issue tracker organized. |
 | Maintainer  | Merges [patch submissions](/contribute). Cuts releases.                                                                |
 | Contributor | Contributed code to the project. Does not imply any current participation or responsibility.                                       |
 

diff --git a/_pages/contribute/index.md b/_pages/contribute/index.md
@@ -8,7 +8,7 @@ nav-links: true
 
 The community encourages discussion about proposed changes on ImageJ's [communication](/help#ways-to-get-help) channels. Submit your ideas!
 
-Start on the [forum](/help), searching for discussions related to your contribution to get some context & background. It can also be helpful to [search](/help#searching-imagej-resources) for applicable issues and plans across the spectrum of ImageJ resources. The ImageJ community believes that [public discussion is important](/develop/philosophy#open-source) so that ideas are exposed to healthy alternate points of view rather than lost.
+Start on the [forum](/discuss), searching for discussions related to your contribution to get some context & background. It can also be helpful to [search](/help#searching-imagej-resources) for applicable issues and plans across the spectrum of ImageJ resources. The ImageJ community believes that [public discussion is important](/develop/philosophy#open-source) so that ideas are exposed to healthy alternate points of view rather than lost.
 
 If you are interested in helping to tackle open issues, see the [wish list](/develop/wish-list) page.
 
@@ -20,7 +20,7 @@ If you are an ImageJ user, contributing documentation is an easy way to give bac
 
 If you are a plugin author, please consider [documenting your plugin on this site](/contribute/distributing#documenting-your-extension). You can have a look at the page [How\_to\_make\_a\_new\_tutorial](/tutorials/make-a-new-tutorial).
 
-When in doubt, discuss your ideas publicly on the Image.sc [Forum](/help)!
+When in doubt, discuss your ideas publicly on the Image.sc [Forum](/discuss)!
 
 ## ImageJ2
 

diff --git a/_pages/develop/debugging-exercises.md b/_pages/develop/debugging-exercises.md
@@ -520,7 +520,7 @@ If a fix is identified:
 
 If a fix is unclear:
 
--   Use any of the standard [channels for help](/help).
+-   Use any of the standard [channels for help](/discuss).
 
 Even if you can't contribute a fix, if you went through the effort of debugging - at the very least you should identify the problem, steps you took to debug, and potential fix(es) via a [bug report](/discuss/bugs) so that your effort is not lost.
 

diff --git a/_pages/develop/maven.md b/_pages/develop/maven.md
@@ -144,7 +144,7 @@ If there are no public repositories containing your dependency, you have two opt
 
 <!-- -->
 
--   If the dependency is narrower in scope, you could [contact the ImageJ & Fiji maintainers](/help/mailing-lists) to get your needed dependency added to the SciJava Maven repository. Note that you will then be responsible for distributing the dependency with your code—so ensure it is [licensed appropriately](/licensing).
+-   If the dependency is narrower in scope, you could [contact the ImageJ & Fiji maintainers](/discuss/mailing-lists) to get your needed dependency added to the SciJava Maven repository. Note that you will then be responsible for distributing the dependency with your code—so ensure it is [licensed appropriately](/licensing).
 
 Finally, for local testing you can [install the dependency into your local Maven repository cache yourself](https://maven.apache.org/guides/mini/guide-3rd-party-jars-local.html). The command is `mvn install:install-file`. For example, if you have a library `foo.jar` to install, you could run:
 
@@ -155,7 +155,7 @@ For the `groupId`, it is typically best to use the reversed domain name of the l
 
 **WARNING:** If you use `install:install-file`, others will not be able to build your code unless they also use `install:install-file` to install the library on their systems.
 
-When in doubt, [contact the community](/help) with your questions.
+When in doubt, [contact the community](/discuss) with your questions.
 
 # Further reading
 

diff --git a/_pages/develop/philosophy.md b/_pages/develop/philosophy.md
@@ -21,7 +21,7 @@ The ImageJ and SciJava communities intend to foster not only scientific *indepen
 
 As such, responses to questions on [ImageJ public channels](/help#ways-to-get-help) will often begin with "What have you tried?" or "Can you make a minimal, complete, verifiable example?"—see the [Bug reporting best practices](/discuss/bugs#bug-reporting-best-practices) for details. A good rule of thumb for questioners is to "put as much effort into your question as you expect to be put into its reply"—and for responders, to cordially encourage this behavior in questioners. Responses may give detailed macro or script solutions to image analysis questions, but they will also often include details of *how such solutions were produced*, as well as *how they might be improved or tailored to other similar scenarios*.
 
-We are always looking for more ways to improve the software to meet this goal of encouraging independent learning. Write to the [ImageJ forum](/help) with your ideas!
+We are always looking for more ways to improve the software to meet this goal of encouraging independent learning. Write to the [ImageJ forum](/discuss) with your ideas!
 
 ## Extensibility
 

diff --git a/_pages/develop/plugins.md b/_pages/develop/plugins.md
@@ -152,7 +152,7 @@ A brief list of some of the more useful plugin types to extend:
 -   {% include github org='scijava' repo='scijava-common' tag='scijava-common-2.47.0' source='org/scijava/module/process/PreprocessorPlugin.java' label='Input Preprocessors' %} give you control over the population of `@Parameters`.
 -   {% include github org='scijava' repo='scijava-common' tag='scijava-common-2.47.0' source='org/scijava/display/Display.java' label='Displays' %} control how UI elements are presented to users.
 
-If you know the function you want to modify but can't determine its location in the code, please [ask other developers.](/help) You're part of the community now!
+If you know the function you want to modify but can't determine its location in the code, please [ask other developers.](/discuss) You're part of the community now!
 
 ## Example projects
 
@@ -275,6 +275,6 @@ Once you have completed plugins and want to get them out to users, you can famil
 -   [The development lifecycle](/develop/releasing)
 -   [Core contribution requirements](/contribute/fiji)
 
-As always, if you ever need assistance, [just ask](/help)!
+As always, if you ever need assistance, [just ask](/discuss)!
 
 
diff --git a/_pages/develop/releasing.md b/_pages/develop/releasing.md
@@ -93,7 +93,7 @@ times to use a topic branch are:
   committing to that API.
 - **Unfinished.** The changes are unfinished.
 - **Regressing.** The changes leave the codebase in a \"worse\" state somehow.
-- **Discussion.** To solicit discussion from the [community](/help),
+- **Discussion.** To solicit discussion from the [community](/discuss),
   especially if the changes might be contentious.
 
 Conversely, some situations to push directly to main:
@@ -151,9 +151,9 @@ The [release-version.sh](https://github.com/scijava/scijava-scripts/blob/master/
 
 -   Install the `release-version.sh` script. The best way to do this is to clone the [SciJava-scripts](https://github.com/scijava/scijava-scripts) repository. That will give you access to other useful scripts and help keep them all up to date.
 -   (**optional**) If you want to easily use these scripts from any directory, you can [add the scijava-scripts folder to your PATH](http://askubuntu.com/q/97897).
--   Verify that your project's parent is pom-scijava version 17.1.1 or newer. If the parent version is too old, or is not pom-scijava, then upgrade it. Ask on the [forum](/help) if you need assistance.
+-   Verify that your project's parent is pom-scijava version 17.1.1 or newer. If the parent version is too old, or is not pom-scijava, then upgrade it. Ask on the [forum](/discuss) if you need assistance.
 -   If your component is to be released to the SciJava Maven repository, then add the following line to the properties section of your POM: <releaseProfiles>`deploy-to-imagej`</releaseProfiles>
--   Ensure the repository for your project is linked with a [Travis CI](/develop/travis) job that automatically builds and deploys Maven artifacts in response to changes on GitHub. If you're not sure if your project has this automation, ask for help on the [forum](/help).
+-   Ensure the repository for your project is linked with a [Travis CI](/develop/travis) job that automatically builds and deploys Maven artifacts in response to changes on GitHub. If you're not sure if your project has this automation, ask for help on the [forum](/discuss).
 
 ### Steps to release
 

diff --git a/_pages/develop/travis.md b/_pages/develop/travis.md
@@ -26,7 +26,7 @@ Deploying your library to a [Maven](/develop/maven) repository makes it availabl
 
 -   Host your [open-source](/Open_Source) project on [GitHub](/develop/github).
 -   Log in to [Travis CI](https://travis-ci.com/auth) with your corresponding GitHub account and enable your repository.
--   Contact an ImageJ admin in [Gitter](/help/chat#gitter) or [the Image.sc Forum](http://forum.image.sc/) and request that they file a PR which adds Travis support to your repository.
+-   Contact an ImageJ admin in [Gitter](/discuss/chat#gitter) or [the Image.sc Forum](http://forum.image.sc/) and request that they file a PR which adds Travis support to your repository.
 
 ## Instructions
 

diff --git a/_pages/discuss/mailing-lists.md b/_pages/discuss/mailing-lists.md
@@ -11,7 +11,7 @@ There are several mailing lists for community discussion and troubleshooting.
 
 Please [search the list archives](http://search.imagej.net/) first to find any previous discussions regarding your problem.
 
-If you have a natural allergy toward subscribing to mailing lists, there are [other ways to get help, too](/help).
+If you have a natural allergy toward subscribing to mailing lists, there are [other ways to get help, too](/discuss).
 
 ## Bugs
 

diff --git a/_pages/downloads.md b/_pages/downloads.md
@@ -57,7 +57,7 @@ That means that you do not have to run an installer; just download, unpack and s
 # Troubleshooting
 
   - Many common questions are answered on the [FAQ](/learn/faq) and [Troubleshooting](/learn/troubleshooting) pages.
-  - If you encounter bugs, please see the [Getting Help](/help) page.
+  - If you encounter bugs, please see the [Getting Help](/discuss) page.
 
 # Source code
 

diff --git a/_pages/events/soc-2009-ideas.md b/_pages/events/soc-2009-ideas.md
@@ -7,7 +7,7 @@ title: SoC 2009 Ideas
 
 Fiji is planning on applying to the Google Summer of Code 2009 program. As mentoring organizations have not yet been accepted, there is no guarantee that Fiji will be asked to participate. This page is to help plan proposed student projects. (UPDATE: Fiji [has been accepted](http://socghop.appspot.com/program/accepted_orgs/google/gsoc2009) as a mentoring organization. See the [Fiji GSoC organization page](http://socghop.appspot.com/org/show/google/gsoc2009/fiji).)
 
-This page contains project ideas culled from the Fiji user and developer community. You can get started by reading some project descriptions, and the mailing list thread(s) that spawned them. Also consider joining the developer mailing list, or finding us on IRC. Details can be found in [Help](/help).
+This page contains project ideas culled from the Fiji user and developer community. You can get started by reading some project descriptions, and the mailing list thread(s) that spawned them. Also consider joining the developer mailing list, or finding us on IRC. Details can be found in [Help](/discuss).
 
 Don't like a project you see here? Just throw your ideas at us, on the developer mailing list!
 
@@ -181,4 +181,4 @@ The project would consist of
 
 * [ImageJ's homepage](/)  
 * [Fiji's developer mailing list](http://groups.google.com/group/fiji-devel)  
-* [#fiji-devel channel](/help/chat#irc) on irc.freenode.net
+* [#fiji-devel channel](/discuss/chat#irc) on irc.freenode.net
diff --git a/_pages/events/soc-2010-ideas.md b/_pages/events/soc-2010-ideas.md
@@ -7,7 +7,7 @@ title: SoC 2010 Ideas
 
 Fiji applied to the Google Summer of Code 2010 program, but was not accepted.
 
-This page contains project ideas culled from the Fiji user and developer community. You can get started by reading some project descriptions, and the mailing list thread(s) that spawned them. Also consider joining the developer mailing list, or finding us on IRC. Details can be found in [Help](/help).
+This page contains project ideas culled from the Fiji user and developer community. You can get started by reading some project descriptions, and the mailing list thread(s) that spawned them. Also consider joining the developer mailing list, or finding us on IRC. Details can be found in [Help](/discuss).
 
 If none of the listed projects suit you, but you have your own project idea instead, just throw your ideas at us, on the developer mailing list! (Of course, it should be related to Fiji...)
 
@@ -310,6 +310,6 @@ This project is about implementing a trainer for such tests, whose result is a m
 
 -   [Fiji's developer mailing list](http://groups.google.com/group/fiji-devel)
 -   [Weka project](http://www.cs.waikato.ac.nz/ml/weka/)
--   [\#fiji-devel channel](/help/chat#irc) on irc.freenode.net
+-   [\#fiji-devel channel](/discuss/chat#irc) on irc.freenode.net
 -   Other [Project ideas](Project_ideas)
 -   [more links](/software/fiji/links)
diff --git a/_pages/formats/dicom.md b/_pages/formats/dicom.md
@@ -50,7 +50,7 @@ An example using `getInfo()`:
     print("Image Position: "+imagePosition);
     print("Pixel Spacing: "+ pixelSpacing);
 
-See also these past threads from the ImageJ [mailing list](/help/mailing-lists):
+See also these past threads from the ImageJ [mailing list](/discuss/mailing-lists):
 
 -   2015-09-23 - [Reading DICOM header without opening the image](http://imagej.1557.x6.nabble.com/Reading-DICOM-header-without-opening-the-image-tp5014426.html)
 -   2013-10-10 - [ImageJ DICOM Header](http://imagej.1557.x6.nabble.com/ImageJ-DICOM-Header-tp5005125.html)

diff --git a/_pages/learn/basics.md b/_pages/learn/basics.md
@@ -19,7 +19,7 @@ nav-links: true
 | [Techniques](/imaging)                     | [Image processing](/ij/docs/guide/146-29.html#toc-Section-29), [colocalization](/imaging/colocalization-analysis), [deconvolution](/imaging/deconvolution), [registration](/imaging/registration), [segmentation](/imaging/segmentation), [tracking](/imaging/tracking), [visualization](/imaging/visualization) and much more. |
 | [Plugins](/plugins)                        | A powerful mechanism for extending ImageJ in all kinds of useful ways. |
 | [Scripting](/scripting)                    | Automated, reproducible workflows via [scripts](/scripting) and [macros](/scripting/macro), including [headless on a remote server or cluster](/scripting/headless). |
-| [Forum](https://forum.image.sc/tag/imagej) | A vibrant, diverse, and helpful user [community](/help) that gives rise to insightful scientific exchanges. |
+| [Forum](https://forum.image.sc/tag/imagej) | A vibrant, diverse, and helpful user [community](/discuss) that gives rise to insightful scientific exchanges. |
 
 ImageJ's [extensibility](/develop/architecture#extensibility) is the root of its effectiveness: many advanced image-processing methods are not provided by the core application, but rather are [plugins](/plugins) written by specialists in specific fields, made available via [update sites](/update-sites).
 

diff --git a/_pages/learn/faq.md b/_pages/learn/faq.md
@@ -431,7 +431,7 @@ As a complete example, if you were interested in the [2D Histogram](/plugins/2d-
 
 ## I have a problem that is not covered on this page!
 
-If you have an issue that is not mentioned here, you might want to [ask on one of the mailing lists, or via IRC](/help), or [enter a bug report](https://fiji.sc/bugzilla/).
+If you have an issue that is not mentioned here, you might want to [ask on one of the mailing lists, or via IRC](/discuss), or [enter a bug report](https://fiji.sc/bugzilla/).
 
 ## How to report issues?