revert magic quotes

Author: jaimergp

docs/maintainer/adding_pkgs.md

@@ -635,7 +635,7 @@ metadata are satisfied.
 `pip check` can sometimes fail due to metadata discrepancies between
 PyPI and conda-forge (e.g. same package with different names). In these
 cases, the reviewer must evaluate whether the error was a false negative.
-Tip: use `pip list` to show what `pip check` “sees”.
+Tip: use `pip list` to show what `pip check` "sees".
 
 :::
 

docs/maintainer/infrastructure.md

@@ -230,7 +230,7 @@ certain very old packages that require VC9 will fail.
 
 TravisCI is used to build packages for IBM Power 8+ and ARM. 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://app.travis-ci.com/account/repositories](https://app.travis-ci.com/account/repositories)
-and click the “Sync accounts” button.
+and click the "Sync accounts" button.
 
 <a id="enabling-travis"></a>
 
@@ -297,7 +297,7 @@ To skip a CI build for a given commit, put `[ci skip] ***NO_CI***` in the commit
 ### Third-party Use of Our CI Services
 
 Due to its stature in the open-source community, conda-forge has enhanced access to certain CI services. This access is a community
-resource entrusted to conda-forge for use in building packages. We thus cannot support third-party or “off-label” CI jobs in our
+resource entrusted to conda-forge for use in building packages. We thus cannot support third-party or "off-label" CI jobs in our
 feedstocks on any of our CI services. If we find such use, we will politely ask the maintainers to rectify the situation. We may
 take more serious actions, including archiving feedstocks or removing maintainers from the organization, if the situation cannot be rectified.
 

docs/maintainer/knowledge_base.md

@@ -58,7 +58,7 @@ Some optional, but useful CMake options:
 - `${CMAKE_ARGS}` Add variables defined by conda-forge internally. This is required to enable various conda-forge enhancements, like [CUDA builds](#cuda).
 
 Here are some basic commands for you to get started. These are dependent on your source
-code layout and aren't intended to be used “as is”.
+code layout and aren't intended to be used "as is".
 
 **CMake lines for build.sh (macOS/Linux):**
 
@@ -159,12 +159,12 @@ versions are:
 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. You can get them from [Visual Studio
+"build tools" packages. You can get them from [Visual Studio
 Subscriptions](https://visualstudio.microsoft.com/vs/older-downloads/#visual-studio-2019-and-other-products).
 To download build tools, you'll need a Microsoft account. Once on the
 Visual Studio Subscriptions page, you may also need to join the Dev Essentials
-program. Once that's done, you can click the “Download” tab and search for
-“Build Tools for Visual Studio 2022”.
+program. Once that's done, you can click the "Download" tab and search for
+"Build Tools for Visual Studio 2022".
 
 If you need more information. Please refer [the Python wiki page on Windows compilers](https://wiki.python.org/moin/WindowsCompilers).
 
@@ -526,7 +526,7 @@ In practical terms, for conda-forge, this results into two extra metadata bits t
     package is being built, like `cython` and `numpy`.
 
 In the terms of the [PEP720](https://peps.python.org/pep-0720/), the conda-forge setup
-implements the “faking the target environment” approach. More specifically, this will result in the
+implements the "faking the target environment" approach. More specifically, this will result in the
 following changes before the builds scripts run:
 
 - A modified `crossenv` installation in `$BUILD_PREFIX/venv`, mimicking the architecture of
@@ -2134,7 +2134,7 @@ higher than the package uploaded with the `dev` label.
 To reset your feedstock token and fix issues with uploads, follow these steps:
 
 1. Go to the `conda-forge/admin-requests` repo and copy [examples/example-broken.yml](https://github.com/conda-forge/admin-requests/blob/main/examples/example-broken.yml) to the `requests/` folder.
-2. Add the name of your feedstock in the YML file. While adding the name, don't add “-feedstock” to the end of it. For example: for `python-feedstock`, just add `python`.
+2. Add the name of your feedstock in the YML file. While adding the name, don't add "-feedstock" to the end of it. For example: for `python-feedstock`, just add `python`.
 
 <a id="using-arch-rebuild"></a>
 

docs/maintainer/maintainer_faq.md

@@ -105,7 +105,7 @@ There is no need to approve the PR. Every maintainer can verify and merge the bo
 
 <a id="how-to-fix-build-locally-py-fails-with-exit-code-139"></a>
 
-## How to fix “build-locally.py fails with exit code 139”?
+## How to fix "build-locally.py fails with exit code 139"?
 
 With Linux Kernel 4.11 there were some changes in the `vsyscall` linking. Depending on your distribution this may cause the above error. You can fix that on Debian by editing `/etc/default/grub` and specifiy `GRUB_CMDLINE_LINUX_DEFAULT="vsyscall=emulate"` in this file. Afterwards, you need to run `update-grub` and reboot your system. On other Linux distributions the fix is similar but you need to edit a different configuration file to change the Linux kernel cmdline. This workaround is only needed for images based on CentOS 6 (`cos6`). You could also workaround this by forcing the CentOS 7 based images using `DOCKER_IMAGE=quay.io/condaforge/linux-anvil-cos7-x86_64 ./build-locally.py`.
 

docs/orga/getting-in-touch.md

@@ -40,7 +40,7 @@ The main chat rooms that you'll interact with are
 * [gitter: core/private](https://gitter.im/conda-forge/core): Private chat for the @conda-forge/core team to discuss continued operations and improvements to conda-forge.
 * [gitter: power pc](https://gitter.im/conda-forge-ppc64le/Lobby): Public chat room for all things related to building for power pc (IBM) systems.
 * [gitter: bot subteam](https://gitter.im/conda-forge/regro-cf-autotick-bot): Public chat room for all things related to the conda-forge automation infrastructure.
-  Our automation infrastructure is colloquially referred to as “the bot”.
+  Our automation infrastructure is colloquially referred to as "the bot".
 * [gitter: compilers](https://gitter.im/conda-forge/conda-forge-compilers): Public chat room focused on the conda-forge compiler stack.
 * [element: conda-forge-space](https://app.element.io/#/room/#conda-forge-space:matrix.org): An element space listing all conda-forge rooms.
 * [element: interns](https://app.element.io/#/room/#conda-forge_conda-forge-interns:gitter.im): Public chat room for conda-forge interns to discuss projects and seek guidance from the community.

docs/orga/governance.md.tmpl

@@ -98,7 +98,7 @@ calling a vote are as follows:
   violating the code of conduct.
 * Voting yes moves the proposal forward;
   voting no is the only way to express opposition to the proposal;
-  not voting is discouraged, but non-votes do not count as “no”.
+  not voting is discouraged, but non-votes do not count as "no".
 * There should always be an option to abstain from voting.
 
 Voting items are labeled as either **standard** or **sensitive**.
@@ -118,7 +118,7 @@ as the authoritative list of emails to use.
 The default voting period is 1 week (7 days). This may be modified at
 the time when a vote is called, but may never be less than 24 hrs.
 
-Additional requirements may apply in case low turnouts have to be handled, see “Quorum” below.
+Additional requirements may apply in case low turnouts have to be handled, see "Quorum" below.
 
 To call for a standard vote, here is a template PR comment:
 
@@ -134,7 +134,7 @@ This vote will end on {date}.
 ---
 * **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
+  "time out" rules below should be recorded in the "vote-results" folder at
   [https://github.com/conda-forge/conda-forge.github.io/tree/main/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
@@ -149,7 +149,7 @@ This vote will end on {date}.
 * **Quorum:**
   Quorum for votes can be met in one of three ways depending on the
   vote: the standard quorum rules, the accelerated quorum rules, and the
-  “time out” quorum rules. The specific quorum rules applicable
+  "time out" quorum rules. The specific quorum rules applicable
   for each vote are listed below.
 
   **Standard Quorum Rules**: All percentages below express *both*
@@ -162,12 +162,12 @@ This vote will end on {date}.
 
   **Accelerated Quorum Rules**: For certain votes, we allow a lower quorum level.
   For these votes,
-  if the voting period is longer than a week and there are no “no” votes, a quorum
+  if the voting period is longer than a week and there are no "no" votes, a quorum
   of half of the size
   needed for a **standard quorum** above is acceptable. For example, for a vote
   requiring 50% with 18
-  active core members, at least 5 people must vote “yes” and exactly 0 people
-  must vote “no”.
+  active core members, at least 5 people must vote "yes" and exactly 0 people
+  must vote "no".
 
   **Time-out Quorum Rules**: Votes not achieving quorum will eventually time out on their set end date.
   When this happens,
@@ -203,7 +203,7 @@ This vote will end on {date}.
       reviews.
       ```
 
-  To declare a standard vote “timed out,” the person making such a declaration
+  To declare a standard vote "timed out," the person making such a declaration
   must post a pull-request adding
   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
@@ -263,7 +263,7 @@ This vote will end on {date}.
   Occasionally, discussions become
   toxic and antithetical to the goal of fostering the conda-forge
   community. Members of core have the right to lock the thread in an
-  “ask for forgiveness and not for permission” way so bad situations
+  "ask for forgiveness and not for permission" way so bad situations
   are handled quickly. The lock must be justified in the thread itself
   with a text explaining the reasons for locking and how the participants
   can contest it.

docs/orga/guidelines.md

@@ -193,10 +193,10 @@ To add new packages to conda-forge, users can submit a PR to `staged-recipes` (s
 where it will undergo a series of automated checks and a code review.
 Any conda-forge member can perform a code review, but the final merge can only be done by the `staged-recipes` or `core` teams.
 The following sections suggest guidelines on how to perform a successful code review.
-We distinguish between “Required” and “Recommended” as follows:
+We distinguish between "Required" and "Recommended" as follows:
 
 - Required: These guidelines are very important and a requisite for PR acceptance. Exceptions are rare and usually require  `core` approval.
-- Recommended: These are considered “nice to have” features. Ideally, all recipes should abide by them, but exceptions are tolerated as long as justifiable reasons are provided.
+- Recommended: These are considered "nice to have" features. Ideally, all recipes should abide by them, but exceptions are tolerated as long as justifiable reasons are provided.
 
 <a id="generalities"></a>
 

docs/orga/joining-the-team.md

@@ -55,10 +55,10 @@ Generally speaking, your role is as follows:
 To join the staged-recipes team, please ask one of the core members on our
 [Element chatroom](https://app.element.io/#/room/#conda-forge:matrix.org).
 We will then reach consensus in private and let you know our decision.
-Our decision will likely be “yes” but it could be “please get more involved
-with the review process on staged recipes first” if we have not seen you
+Our decision will likely be "yes" but it could be "please get more involved
+with the review process on staged recipes first" if we have not seen you
 take much interest in the staged-recipes review process.
-For transparency, our process is to have the core team “vote” on adding new
+For transparency, our process is to have the core team "vote" on adding new
 members. When we have a new member candidate, we ask the core team to vote
 yes/no and give the team seven days to vote. The person will then be given merge
 rights to conda-forge/staged-recipes so that they can help us review and merge

docs/orga/minutes/2017-08-11.md

@@ -22,7 +22,7 @@ Attendees (github handle in parens):
   - Jonathan - create tool for modifying feedstocks directly. Sync up with John K with any additional questions
   - John K - Update staged recipes with new binstar token. We can then update feedstocks by merging the recipe for that feedstock again
   - email to mailing list
-  - add note to status page “We’re aware of this issue. Please take these steps <link> to resolve it”
+  - add note to status page "We’re aware of this issue. Please take these steps <link> to resolve it"
 - Proposing new members for core or staged-recipes team and create reviewing policies
   - https://github.com/conda-forge/staged-recipes/wiki/Reviewing-recipes-on-conda-forge-staged-recipes
 - SciPy Review (Filipe)

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

@@ -62,7 +62,7 @@ Scheduled time: 9 AM central.  Meeting link: https://anaconda.webex.com/anaconda
 | LDFLAGS_SHARED | %LDFLAGS_SHARED% -LTCG ucrt.lib |
 
 
-Overall: everyone receptive to new compilers.  Mike to provide way of keeping host and build prefix separate, even when not cross compiling.  This would avoid need for things like “always_include_files” and would facilitate conda-forge keeping their llvmdev recipe as is (for cling usage).  
+Overall: everyone receptive to new compilers.  Mike to provide way of keeping host and build prefix separate, even when not cross compiling.  This would avoid need for things like "always_include_files" and would facilitate conda-forge keeping their llvmdev recipe as is (for cling usage).  
 
 Filipe: this is really little more than a vendor change.  We already depend on other vendors for compilers (RH for devtoolset2; apple for existing clang), we’re only switching to a different vendor, not fundamentally changing what we do.