added the ability to set custom app icons for windows / macos

.github/ARM32.md

@@ -0,0 +1,42 @@
+# Processing 32-bit Linux
+
+For the Raspberry Pi 3 and older we'd need to create an 32-bit arm version of
+processing.
+
+Github Actions do not support creating 32 bit runners so we need to host one
+ourselves.
+
+## Instructions
+
+### Gathering your Tools
+
+You will need:
+
+- A Raspberry Pi
+- A micro SD card
+- An SD card reader
+- A computer
+
+### Flashing the SD Card
+1. Install and open [**Raspberry Pi Imager**](https://www.raspberrypi.com/software/) on your computer
+2. In **Raspberry Pi Imager**:
+  - Select your Raspberry Pi model
+  - Select "Raspberry PI OS lite (32bit)" as the OS (you may need to look into the sub-menus)
+  - Select your SD card
+  - Click NEXT
+3. Edit the OS settings:
+  - Set a hostname (e.g. `processing.local`)
+  - Set a username and password
+  - Go to the SERVICES tab and enable SSH with password authentication
+  - Click SAVE and Apply the OS customisation settings
+
+### Configuring the Raspberry Pi
+1. Take the written SD card and put it into the Raspberry PI
+2. Power it up and wait for it to boot
+3. SSH into the Raspberry Pi using the hostname, username, and password you set earlier
+4. Follow Github's [instructions on how to set up a self-hosted runner](https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/adding-self-hosted-runners). _Note: In the `./config.sh` setup step, you will be prompted to enter a name and other settings. Use default settings by pressing ENTER for each prompt._
+5. Verify that the new runner appears in the list of runners on GitHub.
+6. Quit the the runner in the terminal (we will set it up to run automatically on boot).
+7. Use Github [instructions to setup the runner as a services](https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/configuring-the-self-hosted-runner-application-as-a-service) so it runs on boot.
+
+Done.

.github/ISSUE_TEMPLATE/1_bug_report.yml

@@ -0,0 +1,93 @@
+name: 🐛 Found a Bug
+description: Report broken or incorrect behavior in Processing 4. (For help with your own code, please visit our forum at discourse.processing.org instead).
+labels: [bug]
+body:
+
+- type: dropdown
+  id: sub-area
+  attributes:
+    label: Most appropriate sub-area of Processing 4?
+    description: You may select more than one.
+    multiple: true
+    options:
+        - Accessibility
+        - Core/Environment/Rendering
+        - PDE
+        - Data
+        - Events
+        - Image
+        - IO
+        - Math
+        - Typography
+        - Utilities
+        - OpenGL
+        - Contributions Manager
+        - Export
+        - Build process
+        - Unit testing
+        - Internationalization
+        - Other (specify if possible)
+  validations:
+    required: true
+
+- type: input
+  attributes:
+    label: Processing version
+    description: Go to "Help > About Processing" and look in the bottom-right corner for the version number. It also appears in the title bar of every editor window.
+  validations:
+    required: true
+
+- type: input
+  attributes:
+    label: Operating system
+    description: "Ex: Windows/MacOSX/Linux/Android/iOS along with version"
+  validations:
+    required: true
+
+- type: textarea
+  attributes:
+    label: Steps to reproduce this
+    description: Describe what steps will produce the bug.
+    value: |
+      "1.
+
+      2.
+
+      3."
+  validations:
+    required: true
+
+- type: textarea
+  attributes:
+    label: snippet
+    description: If applicable, include a minimal sketch that produces the error.
+    value: |
+      ```processing
+
+      // Paste your code below :)
+
+      void setup() {
+
+      }
+
+      void draw() {
+
+      }
+      ```
+  validations:
+    required: false
+
+- type: textarea
+  attributes:
+    label: Additional context
+    description: Add any other context about the problem here.
+  validations:
+    required: false
+
+- type: input
+  attributes:
+    label: Would you like to work on the issue?
+    description: |
+      Please let us know if you can work on this or if the issue should be assigned to someone else.
+  validations:
+    required: true

.github/ISSUE_TEMPLATE/2_enhancement.yml

@@ -0,0 +1,74 @@
+name: 💡 Existing Feature Enhancement
+description: Suggest an improvement for an existing feature of Processing.
+labels: [enhancement]
+body:
+
+- type: dropdown
+  id: feature-area
+  attributes:
+    label: Most relevant area for this enhancement?
+    description: Choose the most relevant area for the proposed feature or improvement.
+    multiple: true
+    options:
+        - Accessibility
+        - Core/Environment/Rendering
+        - PDE
+        - Data
+        - Events
+        - Image
+        - IO
+        - Math
+        - Typography
+        - Utilities
+        - OpenGL
+        - Contributions Manager
+        - Export
+        - Build process
+        - Unit testing
+        - Internationalization
+        - Other (specify if possible)
+  validations:
+    required: true
+
+- type: input
+  attributes:
+    label: Feature to enhance
+    description: Which existing feature of Processing would be improved by this enhancement?
+  validations:
+    required: true
+
+- type: textarea
+  attributes:
+    label: Desired enhancement
+    description: Describe the improvement you’d like to see with that existing feature
+  validations:
+    required: true
+
+- type: textarea
+  attributes:
+    label: Potential benefits
+    description: Explain how this enhancement could benefit users or improve Processing.
+  validations:
+    required: false
+
+- type: textarea
+  attributes:
+    label: Possible drawbacks
+    description: Consider any possible drawbacks or challenges related to the implementation of this enhancement.
+  validations:
+    required: false
+
+- type: textarea
+  attributes:
+    label: Additional context
+    description: Add any other context or screenshots about the feature request here.
+  validations:
+    required: false
+
+- type: input
+  attributes:
+    label: Would you like to work on the issue?
+    description: |
+      Please let us know if you can work on this or if the issue should be assigned to someone else.
+  validations:
+    required: true

.github/ISSUE_TEMPLATE/3_feature-request.yml

@@ -0,0 +1,72 @@
+name: 🌱 New Feature Request
+description: Request adding a new feature to Processing
+labels: [new feature]
+body:
+
+- type: dropdown
+  id: feature-area
+  attributes:
+    label: Relevant sub-area for this feature?
+    description: Choose the sub-area most relevant to your feature request.
+    multiple: true
+    options:
+      - Accessibility
+      - Core/Environment/Rendering
+      - PDE
+      - Data
+      - Events
+      - Image
+      - IO
+      - Math
+      - Typography
+      - Utilities
+      - OpenGL
+      - Contributions Manager
+      - Export
+      - Build process
+      - Unit testing
+      - Internationalization
+      - Other (specify if possible)
+  validations:
+    required: true
+
+- type: textarea
+  id: feature-description
+  attributes:
+    label: Feature description
+    description: Describe the feature in detail. Include how it should work and its intended impact.
+  validations:
+    required: true
+
+- type: textarea
+  id: benefits
+  attributes:
+    label: Benefits
+    description: Outline how this feature would benefit users or improve Processing.
+  validations:
+    required: true
+
+- type: textarea
+  id: challenges
+  attributes:
+    label: Possible challenges
+    description: Discuss any possible challenges or considerations in implementing this feature.
+  validations:
+    required: false
+
+- type: textarea
+  id: additional-context
+  attributes:
+    label: Additional context
+    description: Provide any other information, links, or screenshots that could help illustrate the feature.
+  validations:
+    required: false
+
+
+- type: input
+  attributes:
+    label: Would you like to work on the issue?
+    description: |
+      Please let us know if you can work on this or if the issue should be assigned to someone else.
+  validations:
+    required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,14 @@
+blank_issues_enabled: true
+contact_links:
+  - name: 🌐 Processing Website Issues
+    url: https://github.com/processing/processing-website/issues
+    about: Report issues with the processing.org website here.
+  - name: 📚 Examples Issues
+    url: https://github.com/processing/processing-examples/issues
+    about: Report issues with the official Processing examples here.
+  - name: 💬 Forum
+    url: https://discourse.processing.org/
+    about: Have other questions about using Processing? Ask them here!
+  - name: 🌸 p5.js Issues
+    url: https://github.com/processing/p5.js/issues
+    about: Report issues with p5.js here.

.github/release.yml

@@ -0,0 +1,19 @@
+changelog:
+  exclude:
+    labels:
+      - Dependencies
+    authors:
+      - dependabot
+  categories:
+    - title: What's Changed 🎊
+      labels:
+        - '*'
+      exclude:
+        labels:
+          - Dependencies
+        authors:
+          - allcontributors
+          - dependabot
+    - title: New Contributors 💙
+      authors:
+        - allcontributors