Merge pull request #1565 from croth1/link_cleanup

[WIP] Clean up broken bits and links in the docs

Author: beckermr

src/maintainer/infrastructure.rst

@@ -25,7 +25,7 @@ Smithy contains maintenance code for conda-forge, which is used by the ``conda-s
 
 ``conda-smithy`` also contains the command line tool that you should use if you rerender manually from the command line (see :ref:`dev_update_rerender`).
 
-Smithy can be used beyond Conda-Forge's purposes. For example, it can be used to `set up self-hosted Azure agents <self-hosted_azure-config>`__ for non-Conda-Forge infrastructures.
+Smithy can be used beyond Conda-Forge's purposes. For example, it can be used to `set up self-hosted Azure agents <azure-config>` for non-Conda-Forge infrastructures.
 (You could also consider using `Azure virtual machine scale set agents <https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/scale-set-agents?view=azure-devops>`_,
 which could be less expensive to run than permanently active agents.)
 
@@ -210,8 +210,8 @@ TravisCI (OSX, IBM Power 8+)
 ------------------------------
 
 TravisCI is used to build packages for IBM Power 8+. After merging a staged-recipes pull request, it might be necessary to
-force sync your repositories in TravisCI to see the reload and cancel buttons. To do this please visit `<https://travis-ci.com/profile>`_
-and click "Sync accounts".
+force sync your repositories in TravisCI to see the reload and cancel buttons. To do this please visit `<https://app.travis-ci.com/account/repositories>`__
+and click the "Sync accounts" button.
 
 Enabling Travis
 ...............
@@ -254,15 +254,8 @@ CircleCI for OSX should be used for OSX, only when TravisCI resources (50 minute
 Note that you need to rerender the feedstock, once this change has been made.
 
 
-Enabling Circle on your Fork
-............................
-
-If for some reason CircleCI is not triggering build from forks,
-Circle can be manually added for each fork. Circle calls this "Adding a Project" and
-`the official CircleCI documentation is available here <https://circleci.com/docs/getting-started/#add-and-follow-more-projects>`__.
-This effectively amounts to going to the `Add Projects <https://circleci.com/add-projects>`__
-page, finding the fork that you wish to enable, and clicking the "Build Project" button.
-This is not normally needed.
+Debugging permission errors
+...........................
 
 If CircleCI lacks permissions to checkout the source code, it will produce an error as follows::
 
@@ -271,7 +264,7 @@ If CircleCI lacks permissions to checkout the source code, it will produce an er
     Permission denied (publickey).
     fatal: Could not read from remote repository.
 
-When this happens for a feedstock, it can be fixed using the `webservice <https://conda-forge.org/docs/webservice.html#conda-forge-admin-please-update-circle>`__, by posting the following comment::
+When this happens for a feedstock, it can be fixed using the `webservice <ci_update_circle>`, by posting the following comment::
 
   @conda-forge-admin, please update circle
 

src/maintainer/knowledge_base.rst

@@ -124,18 +124,15 @@ compiled libraries used in Python, `as described on this Python wiki page
 <https://wiki.python.org/moin/WindowsCompilers>`__. The current relevant
 versions are:
 
-* For Python 2.7: Visual C++ 9.0
 * For Python 3.5–3.7: Visual C++ 14.0
 
 While you can obtain these tools by installing the right version of the full
 `Visual Studio <https://visualstudio.microsoft.com/>`__ development
 environment, you can save a lot of time and bandwidth by installing standalone
 “build tools” packages. The links are as follows:
 
-* For Python 2.7: `Microsoft Visual C++ Compiler for Python 2.7
-  <https://www.microsoft.com/download/details.aspx?id=44266>`__.
 * For Python 3.5–3.7: `Microsoft Build Tools for Visual Studio 2017
-  <https://www.visualstudio.com/downloads/#build-tools-for-visual-studio-2017>`__.
+  <https://visualstudio.microsoft.com/vs/older-downloads/#visual-studio-2017-and-other-products>`__.
 
 If you need more information. Please refer `the Python wiki page on Windows compilers
 <https://wiki.python.org/moin/WindowsCompilers>`__.

src/maintainer/maintainer_faq.rst

@@ -148,7 +148,7 @@ FAQ
 
 
 
-  This comes from the CI environment being headless and can be fixed by adding the ``QT_QPA_PLATFORM=offscreen`` `environment variable <https://docs.conda.io/projects/conda-build/en/latest/user-guide/environment-variables.html#inherited-environment-variabless>`_.
+  This comes from the CI environment being headless and can be fixed by adding the ``QT_QPA_PLATFORM=offscreen`` `environment variable <https://docs.conda.io/projects/conda-build/en/latest/user-guide/environment-variables.html#inherited-environment-variables>`__.
   The variable can either be added directly to the test command or provided in the `meta.yaml <https://conda-forge.org/docs/maintainer/adding_pkgs.html#the-recipe-meta-yaml>`__ like so:
 
   .. code-block:: yaml

src/maintainer/pinning_deps.rst

@@ -118,6 +118,6 @@ be added by hand. To do this, follow these steps:
      - Bump the version in meta.yaml to the current date
 
 Details of how the migration yaml is setup are provided in an `example <https://github.com/conda-forge/conda-forge-pinning-feedstock/tree/master/recipe/migrations/example.exyaml>`__
-and documentation `here <https://regro.github.io/cf-scripts/migrators.html#building-a-migration-yaml>`_.
+and documentation `here <https://regro.github.io/cf-scripts/migrators.html#making-migrators>`_.
 
 .. _conda-forge/conda-forge-pinning-feedstock: https://github.com/conda-forge/conda-forge-pinning-feedstock

src/misc/00_intro.rst

@@ -7,13 +7,13 @@ Glossary
 .. glossary::
 
   CI
-    **C**\ ontinuous **I**\ ntegration. Continuous integration is the practice of automating the integration of code changes from multiple contributors into a single software project. `Learn More <https://en.wikipedia.org/wiki/Continuous_integration/>`__.
+    **C**\ ontinuous **I**\ ntegration. Continuous integration is the practice of automating the integration of code changes from multiple contributors into a single software project. `Learn More <https://en.wikipedia.org/wiki/Continuous_integration>`__.
 
   PR
     **P**\ ull **R**\ equest. Pull Request is a workflow method to submit contributions to an open development project in which the developer asks for changes committed to an external repository to be considered for inclusion in a project's main repository. `Learn More <https://help.github.com/articles/about-pull-requests/>`__.
 
   CDT
-    **C**\ ore **D**\ ependency **T**\ ree. Core Dependency Tree packages take care of the dependencies which are so close to the system that they are not packaged with ``conda-forge``. A CDT package consists of repackaged CentOS binaries from the appropriate version, either 6 or 7 depending on user choice and platform. `Learn More <https://conda-forge.org/docs/maintainer/knowledge_base.html#core-dependency-tree-packages-cdts/>`__.
+    **C**\ ore **D**\ ependency **T**\ ree. Core Dependency Tree packages take care of the dependencies which are so close to the system that they are not packaged with ``conda-forge``. A CDT package consists of repackaged CentOS binaries from the appropriate version, either 6 or 7 depending on user choice and platform. :ref:`Learn more<cdt_packages>`.
 
   ABI
     **A**\ pplication **B**\ inary **I**\ nterface. ABI is a document that comprehensively defines the binary system interface between applications and the operating system on which they run. `Learn More <https://en.wikipedia.org/wiki/Application_binary_interface>`__.
@@ -31,5 +31,3 @@ TODO list
 *********
 
 .. todolist::
-
-The original entry is located in ``.src`` file of `/home/runner/work/conda-forge.github.io/conda-forge.github.io/src/maintainer/knowledge_base.rst, line 952. <https://github.com/conda-forge/conda-forge.github.io/blob/main/src/maintainer/knowledge_base.rst#noarch-generic/>`__.

src/orga/governance.rst

@@ -86,8 +86,8 @@ Standard items are ones where public record and discourse is
 preferable. Sensitive voting items are ones where the results of the
 vote should remain private to the voters after the vote has occurred.
 Sensitive votes should take place on a secure anonymous voting platform
-in order to retain election integrity and anonymity. (We have used `Polys <polys.me>`_
-and `the Helios voting system <https://vote.heliosvoting.org/>`_, but are
+in order to retain election integrity and anonymity. (We have used `Polys <https://polys.me>`__
+and `the Helios voting system <https://vote.heliosvoting.org/>`__, but are
 open to any secure, anonymous system.) The email capability of your chosen
 voting platform should be used for sending voting invitations and reminders,
 and you should use the email list from
@@ -114,7 +114,7 @@ To call for a standard vote, here is a template PR comment:
 
 :Posting results: To maintain the historical record, the outcome of any standard vote which invokes the
          "time out" rules below should be recorded in the "vote-results" folder at
-         https://github.com/conda-forge/conda-forge.github.io/tree/main/src/vote-results
+         https://github.com/conda-forge/conda-forge.github.io/tree/main/vote-results
 
          Each vote should be its own file.  The filename should reflect the topic and the
          date that the vote opened.  The file should contain at least:
@@ -187,8 +187,8 @@ To call for a standard vote, here is a template PR comment:
 
      To declare a standard vote "timed out," the person making such a declaration
      must post a pull-request adding
-     a vote record to the https://github.com/conda-forge/conda-forge.github.io/tree/main/src/vote-results
-     folder.  The declaration PR should be merged by the first core member
+     a vote record to the `vote-results folder <https://github.com/conda-forge/conda-forge.github.io/tree/main/vote-results>`__.  
+     The declaration PR should be merged by the first core member
      who is available to verify that
      the requirements for the timeout have been met, based on their
      own personal records.

src/orga/minutes/2017-11-16.md

@@ -2,7 +2,7 @@
 Scheduled time: 9 AM central.  Meeting link: https://anaconda.webex.com/anaconda-en/j.php?MTID=m11b5ddad66325da22bbe58d7d1c02809
 
 
-# Adopting Anaconda compilers
+## Adopting Anaconda compilers
 - Linux: gcc 7.2
     - Prefixed compilers: require activation
     - Common adaptations required for new anaconda compilers:
@@ -20,7 +20,7 @@ Scheduled time: 9 AM central.  Meeting link: https://anaconda.webex.com/anaconda
     import os
 
     print("Hello World")
-# Compiler flag unification
+## Compiler flag unification
 - GCC
     - toolchain: https://github.com/conda-forge/toolchain-feedstock/blob/master/recipe/activate.sh
     - toolchain3: https://github.com/conda-forge/toolchain3-feedstock/blob/master/recipe/activate.sh
@@ -65,7 +65,7 @@ Filipe: this is really little more than a vendor change.  We already depend on o
 
 Need to maintain llvm with cling patches, but this will not be the default compiler.
 
-# Conda-build 3: strategy for moving
+## Conda-build 3: strategy for moving
 - install and use with c-b-a (no cb3 matrix)
     - Waiting on feedback from issue https://github.com/conda-tools/conda-build-all/issues/94 but mostly seems OK.
 - Mike: needs to fix —skip-existing.  Concern is that re-rendering should not generate new packages when only some dependency has changed (bugfix bump?)
@@ -82,13 +82,13 @@ Need to maintain llvm with cling patches, but this will not be the default compi
     - People generally interested, but needs to be implemented and proven over time.  Good experience so far with defaults.
 
 
-# Fortran support on Windows
+## Fortran support on Windows
 - gfortran (msys2) / Flang
 - Timeline for adding either
 - Mike asked that whatever is done is done with community approval, for the sake of maintaining a high quality user experience.
 
 
-# OpenMP behavior
+## OpenMP behavior
 - Currently, needs extra package on mac, but is included on Linux (not active in flags, though)
 - What is desirable default behavior?
 

src/orga/minutes/2019-07-24.md

@@ -1,4 +1,4 @@
-# 2017-07-24 conda-forge core meeting 
+# 2019-07-24 conda-forge core meeting 
 
 [HackMD link](https://hackmd.io/P8on5P8wR3q3WslwrJzOEg)
 ## Attendees

src/orga/minutes/2019-08-07.md

@@ -1,4 +1,4 @@
-# 2017-08-07 conda-forge core meeting 
+# 2019-08-07 conda-forge core meeting 
 
 [HackMD link](https://hackmd.io/1VB13FnIQpiruA0lb04MKw?edit)