NYCCHKBK-12891: Drupal 9 release

CODE_OF_CONDUCT.md

@@ -2,75 +2,99 @@
 
 ## Our Pledge
 
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, sex characteristics, gender identity and expression,
-level of experience, education, socio-economic status, nationality, personal
-appearance, race, religion, or sexual identity and orientation.
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for 
+everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity 
+and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, 
+color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
 
 ## Our Standards
 
-Examples of behavior that contributes to creating a positive environment
-include:
+Examples of behavior that contributes to a positive environment for our community include:
 
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
+    Demonstrating empathy and kindness toward other people
+    Being respectful of differing opinions, viewpoints, and experiences
+    Giving and gracefully accepting constructive feedback
+    Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+    Focusing on what is best not just for us as individuals, but for the overall community
 
-Examples of unacceptable behavior by participants include:
+Examples of unacceptable behavior include:
 
-* The use of sexualized language or imagery and unwelcome sexual attention or
- advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
- address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
- professional setting
+    The use of sexualized language or imagery, and sexual attention or advances of any kind
+    Trolling, insulting or derogatory comments, and personal or political attacks
+    Public or private harassment
+    Publishing others’ private information, such as a physical or email address, without their explicit permission
+    Other conduct which could reasonably be considered inappropriate in a professional setting
 
-## Our Responsibilities
 
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
+## Enforcement Responsibilities
 
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior 
+and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, 
 threatening, offensive, or harmful.
 
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, 
+issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for 
+moderation decisions when appropriate.
+
 ## Scope
 
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing 
+the community in public spaces. Examples of representing our community include using an official e-mail address, 
+posting via an official social media account, or acting as an appointed representative at an online or offline event.
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at [email protected]. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
 
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible 
+for enforcement at [email protected]. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem 
+in violation of this Code of Conduct:
+
+1. Correction
+
+Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and 
+an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+2. Warning
+
+Community Impact: A violation through a single incident or series of actions.
+
+Consequence: A warning with consequences for continued behavior. No interaction with the people involved, including 
+unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding 
+interactions in community spaces as well as external channels like social media. Violating these terms may lead to a 
+temporary or permanent ban.
+
+3. Temporary Ban
+
+Community Impact: A serious violation of community standards, including sustained inappropriate behavior.
+
+Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified 
+period of time. No public or private interaction with the people involved, including unsolicited interaction with those 
+enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+4. Permanent Ban
+
+Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, 
+harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+Consequence: A permanent ban from any sort of public interaction within the community.
+
 
 ## Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+This Code of Conduct is adapted from the Contributor Covenant, version 2.1, 
+available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
 
-[homepage]: https://www.contributor-covenant.org
+Community Impact Guidelines were inspired by Mozilla’s code of conduct enforcement ladder.
 
-For answers to common questions about this code of conduct, see
-https://www.contributor-covenant.org/faq
+For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. 
+Translations are available at https://www.contributor-covenant.org/translations.

INSTALL.md

@@ -24,7 +24,7 @@ standardize deployment, and we are conducting that work in the open,
 with participation from all interested parties.  The code's authors,
 who are intimately familiar with every step of the process, naturally
 can and do regularly deploy production instances to
-<http://checkbooknyc.com/> -- but various improvements need to be made
+<https://www.checkbooknyc.com/> -- but various improvements need to be made
 to these instructions before that process is equally easy for
 newcomers.
 
@@ -45,26 +45,25 @@ Requirements
 Please note that unlike most Drupal-based applications, Checkbook uses
 two separate databases simultaneously:
 
- * MySQL for the application itself (essentially Drupal + some modules)
+ * MySQL/MariaDB for the application itself (essentially Drupal + some modules)
  * PostgreSQL for the financial data (usually much larger than the app)
 
 The full list of dependencies is:
 
  * GNU/Linux or similar operating system
- * Drupal 7.x  _(Note: Checkbook includes Drupal, so don't download Drupal separately.)_
- * PHP 5.3 or higher
- * MySQL 5.0.15 or higher (<http://www.mysql.com/> -- we have not tested
-   with a drop-in replacement such as MariaDB <https://mariadb.org/>
-   but would be interested to know if it works)
- * PostgreSQL 8.3 or higher (<http://www.postgresql.org/> -- any
-   database that supports PostgresSQL is compatible for storing
-   Checkbook data (e.g., PostgreSQL, Greenplum)
+ * Drupal 9.5  _(Note: Checkbook includes Drupal, so you don't need to download Drupal separately.)_
+ * PHP 8.1.6 or higher with the following extensions enabled:
+   - PHP Intl extension (<https://www.php.net/manual/en/intl.setup.php>)
+   - PHP PostgreSQL extension (<https://www.php.net/manual/en/pgsql.setup.php>)
+ * MySQL 5.7.8 or higher (<https://www.mysql.com/>) or
+   MariaDB 10.3.7 or higher (<https://mariadb.org/>)
+ * PostgreSQL 9.2 or higher (<https://www.postgresql.org/>) -- other
+   data warehouse products derived from PostgreSQL (e.g. Greenplum Database,
+   Amazon Redshift) are also compatible for storing Checkbook data
  * psql client (PostgreSQL command line interface)
- * Apache HTTPD with following PHP extensions
-   - PHP Intl extension (<http://php.net/manual/en/intl.setup.php>)
-   - PHP PostgreSQL extension (<http://www.php.net/manual/en/pgsql.setup.php>)
- * Solr 4.* search platform (<http://lucene.apache.org/solr/>)
- * Drush version 5.0 (Drupal command-line scripting tool)
+ * Apache HTTPD 2.4.7 or higher with mod_rewrite enabled
+ * Solr 7.4.x search platform (<https://solr.apache.org/>)
+ * Drush 11.x (Drupal command-line scripting tool)
 
 The Checkbook distribution includes the Drupal source tree, along with
 additional (non-core) custom and contributed Drupal modules used by
@@ -76,28 +75,27 @@ Optional configuration for scalability and performance
 ------------------------------------------------------
 
 These instructions assume you're deploying Checkbook on a single
-server, that is, where httpd, the databases, and Tomcat+Solr are all
-running on one machine.
+server, that is, where httpd, the databases, and Solr are all running
+on a single instance.
 
 While this is okay for test deployments, in production you might want
-to divide services among multiple machines, and (for example) use:
+to divide services among multiple instances, and (for example) use:
 
  * A load balancer for distributing requests across multiple instances.
  * Varnish or any other reverse proxy cache for caching last access pages.
- * PGPool for distributing load across multiple PostgreSQL or
-   Greenplum databases.
+ * PGPool for distributing load across multiple PostgreSQL databases.
 
 If you are configuring for scalability and performance in this way,
 then parts of the instructions below will need adjustment, of course.
 
 Installation
 ------------
 
-We assume that a GNU/Linux server with LAMP stack is installed.
+We assume that a GNU/Linux server with basic system utilities is installed.
 The following assumptions are also made about the installation:
 
- * The webroot is `/var/www/html`.
-   (It could be somewhere else; `/var/www/html` is just the location
+ * The webroot is `/var/www/html`
+   (It could be somewhere else; `/var/www/html` is just the standard location
    we use in these instructions.)
 
 The initial installation of the GNU/Linux server with LAMP stack takes on average 20 minutes.
@@ -116,21 +114,16 @@ Steps to install:
 
 2.  Ensure you have the necessary dependencies installed.
 
-    On Ubuntu 12.04 Server, that looks like this (Debian GNU/Linux
-    should be pretty similar):
+    On Ubuntu 22.04, you can install the necessary packages like this
+    (Debian GNU/Linux should be pretty similar):
 
         $ sudo apt-get update
-        $ sudo apt-get install php5
-        $ sudo apt-get install php5-gd
-        $ sudo apt-get install php5-intl
-        $ sudo apt-get install php5-mysql
-        $ sudo apt-get install php5-pgsql
+        $ sudo apt-get install apache2 php8.1 php8.1-gd php8.1-intl php8.1-mysql php8.1-pgsql
         $ sudo apt-get install mysql-server
         $ sudo apt-get install postgresql
         $ sudo apt-get install postgresql-client
         $ sudo apt-get install postgresql-contrib
         $ sudo apt-get install git
-        $ sudo apt-get install drush
         $ sudo apt-get install apache2
         $ sudo apt-get install openjdk-6-jre-headless
         $ sudo apt-get install zip