Merge branch 'main' into update-roles-permissions

Author: viniciusdc

.github/ISSUE_TEMPLATE/documentation.yml

@@ -28,6 +28,7 @@ body:
       options:
         - label: "This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/nebari-dev/nebari/discussions"
           required: true
+
   - type: textarea
     validations:
       required: true
@@ -37,19 +38,6 @@ body:
         What problem(s) did you run into that caused you to request a fix to the documentation or additional
         documentation? What questions do you think we should answer?
 
-  - type: textarea
-    validations:
-      required: true
-    attributes:
-      label: Steps to Resolve this Issue
-      description: |
-        How can the problem be solved? Are there any additional steps required? Do any other pages need to be updated?
-      value: |
-        1.
-        2.
-        3.
-        ...
-
   - type: markdown
     attributes:
       value: >

.github/workflows/test-website.yml

@@ -19,7 +19,7 @@ jobs:
         run: echo "::set-output name=dir::$(yarn cache dir)"
 
       - name: Cache dependencies 🧪
-        uses: actions/cache@v2
+        uses: actions/cache@v4
         id: yarn-cache
         with:
           path: ${{ steps.yarn-cache-dir-path.outputs.dir }}

.pre-commit-config.yaml

@@ -17,7 +17,7 @@ ci:
 repos:
   # Codespell: Spell checks the code and documentation
   - repo: https://github.com/codespell-project/codespell
-    rev: v2.3.0
+    rev: v2.4.1
     hooks:
       - id: codespell
         entry: codespell
@@ -36,7 +36,7 @@ repos:
 
   # Misc...
   - repo: https://github.com/pre-commit/pre-commit-hooks
-    rev: v5.0.0
+    rev: v6.0.0
     # ref: https://github.com/pre-commit/pre-commit-hooks#hooks-available
     hooks:
       # Autoformat: Makes sure files end in a newline and only a newline

docs/.eslintignore

@@ -107,7 +107,7 @@ We have a:
 * weekly 30-minute triage meeting where we triage and follow-up on open issues and PRs.
 
 The embedded Google Calendar below shows the meeting schedules.
-Click on the meeting event in the calendar to find more details like the [Google Meet link](https://meet.google.com/ijt-fveo-nvx), or to copy the event to your personal calendar.
+Click on the meeting event in the calendar to find more details like the meeting link, or to copy the event to your personal calendar.
 
 <iframe src="https://calendar.google.com/calendar/embed?src=c_47708599e46a75c4d54f087e881a43b57e3245da5d9cb2011695da55d481e69f%40group.calendar.google.com" width="800" height="600" frameborder="0" scrolling="no"></iframe>
 

docs/community/introduction.mdx

@@ -63,3 +63,19 @@ Nebari follows a nomination process to add new team members[^2], as detailed in
 | Contributor | Two or more [contributions](/community/introduction/#how-to-contribute) to Nebari with intention to continue contributing regularly           | Any community member (including self)                          | Any Core team member                                                                                  |
 | Core        | [Contributors team](#contributors) member with a record of regular, valuable, and high-quality contributions to Nebari for at least one month | Any community member (including self) and one Core team member | Core team makes a [consent-based decision](https://www.sociocracyforall.org/consent-decision-making/) |
 | Conduct     | Member of the Contributor or Core Team with adequate training to handle CoC reports                                                           | Any community member (including self)                          | Core team makes a [consent-based decision](https://www.sociocracyforall.org/consent-decision-making/) |
+
+Before approving the nomination, Core team members must verify the individual's authenticity and credentials through heuristics like:
+
+- Checking the nominee's GitHub activity history: account creation date, contributions to other open source projects, etc.
+- Interactions with the nominee in community meetings or conferences.
+- Endorsement from a trusted collaborator.
+
+The Owners team is responsible for updating team memberships on GitHub.
+
+## Leave a team
+
+Contributors and Core team members may choose to leave their respective teams at any time and for any reason. They can communicate their decision either privately to the Core team or publicly on the Nebari discussion forum.
+
+To ensure project security, the Core team can make a [consent-based decision](https://www.sociocracyforall.org/consent-decision-making/) to remove inactive members from any team. In this context, _inactive_ refers to individuals who have not engaged in any Nebari spaces, such as GitHub repositories under the Nebari organization or community meetings, for a period of over two months.
+
+The Owners team is responsible for updating team memberships accordingly and documenting the changes in the Nebari discussion forum. By default, former Core team members are added to the Emeritus team unless they explicitly request otherwise.

docs/community/team-structure.md

@@ -155,7 +155,7 @@ jupyterlab:
 
 - `jupyterlab.preferred_dir` - Sets the default location in which JupyterLab should open the file browser in.
 
-- `jupyterlab.gallery_settings` - Configures [`jupyterlab-gallery`](https://github.com/nebari-dev/jupyterlab-gallery) extension which enables user to clone (and later synchronise) pre-specified repositories.
+- `jupyterlab.gallery_settings` - Configures [`jupyterlab-gallery`](https://github.com/nebari-dev/jupyterlab-gallery) extension which enables user to clone (and later synchronise) pre-specified repositories. See [How to set up a Git Repository via JupyterLab-Gallery](../how-tos/jupyter-gallery) for more detailed information.
 
 ```yaml
 jupyterlab:

docs/docs/explanations/advanced-custom-settings.md

@@ -78,7 +78,25 @@ google_cloud_platform:
 
 ##### Amazon Web Services
 
-Spot instances aren't supported at this moment.
+```yaml
+amazon_web_services:
+  kubernetes_version: '1.31'
+  region: us-east-2
+  availability_zones:
+    - us-east-2a
+    - us-east-2b
+  node_groups:
+  # ...
+    spot-instance-group:
+      instance: m5.2xlarge
+      min_nodes: 1
+      max_nodes: 1
+      taints:
+      gpu: false
+      single_subnet: false
+      spot: true
+      permissions_boundary:
+```
 
 ##### Azure
 

docs/docs/faq.md

@@ -0,0 +1,105 @@
+---
+title: Share Git Repository via JupyterLab-Gallery
+description: Share files or tutorials with your team
+---
+
+# How to set up a Git Repository via JupyterLab-Gallery
+
+[JupyterLab-Gallery ](https://github.com/nebari-dev/jupyterlab-gallery) is a JupyterLab plugin
+that allows users to share a Git Repository. JupyterLab users are presented with a tile in
+the JupyterLab launch screen. Users can choose to download the Exhibit.
+
+By default, if no JupyterLab-Gallery items are added to the config, users will not see this section
+in the JupyterLab Launcher.
+
+This feature was added to Nebari in the 2024.6.1 release.
+
+## Configure JupyterLb-Gallery
+
+In Nebari, the JupyterLab-Gallery configuration is set in the Nebari configuration, `nebari-config.yaml`.
+
+The configuration is set under the `jupyterlab` section under the subsection `gallery_settings`.
+Users may set a title for the Gallery section of the Launcher screen and a destination (i.e. folder)
+for the location of the cloned repos.
+
+Several repositories can be configured to display as individual gallery tiles. Under the `exhibits`
+section, each repository must have a `title` and a `git` location. There are also several other
+optional config options.
+
+The configuration is set at two different levels. Top level gallery settings define the title of
+the Gallery section and the location in which the repositories are downloaded. The repository
+level settings are defined for each repository. The settings in each section are described
+below.
+
+**Top Level Gallery Settings**
+
+| Section     | Description                                        |
+| ----------- | -------------------------------------------------- |
+| title       | Title on the gallery tile                          |
+| destination | Location on disk where the repo will be downloaded |
+
+**Repository Level Settings**
+
+| Section     | Description                                                                         |
+| ----------- | ----------------------------------------------------------------------------------- |
+| title       | Title on the gallery tile                                                           |
+| git         | URL of the git repository                                                           |
+| homepage    | (Optional)                                                                          |
+| description | Description of the repository to appear on the gallery tile (Optional)              |
+| icon        | URL or base64 encoded image to use an icon to appear on the gallery tile (Optional) |
+| account     | (Optional)                                                                          |
+| token       | Private Access Token to enable access to private repositories (Optional)            |
+
+### Sample configuration
+
+Below is an example of the Gallery settings from the `nebari-config.yaml`. Note that \<encoding\>
+and \<PAT\> should be replaced with the actual encoding and Private Access Token, respectively.
+
+```
+jupyterlab:
+  gallery_settings:
+    title: Demos
+    destination: demos
+    exhibits:
+    - title: Data of an Unusual Size
+      git: https://github.com/nebari-dev/big-data-tutorial.git
+      description: Big data tutorial focusing on Dask usage in Nebari
+      icon: "data:image/png;base64,<encoding>"
+      homepage: https://github.com/nebari-dev/big-data-tutorial/
+    - title: From RAGs to riches
+      git: https://github.com/Quansight/ragna-presentations.git
+      homepage: https://github.com/Quansight/ragna-presentations/
+    - title: Private Examples
+      description: Internal company examples
+      icon: "data:image/png;base64,<encoding>"
+      git: https://gitlab....net/companyxyz/examples.git
+      account: examples
+      token: "<PAT>"
+```
+
+## Using JupyterLab-Gallery
+
+Once the repositories are configured in the Nebari config and redeployed, all users will have
+a section on their JupyterLab Launcher screen for the Gallery.
+
+![JupyterLab Gallery tiles on JupyterLab Launcher screen](/img/how-tos/jupyter-gallery-tiles.png)
+
+Each tile points to a different gallery entry in the configuration. The Gallery repositories
+will not be downloaded until users trigger the download for each gallery item. To do so, users
+will hover over the tile and click the download button.
+
+![JupyterLab Gallery tile on hover for undownloaded repo](/img/how-tos/jupyter-gallery-tile-download.png)
+
+The repository will download to the location specified in the config (in each user's private
+space). After the download is complete, hover on the gallery tile present the users with two
+new options - the folder icon allows them to jump to the location in the JupyterLab file browser,
+and the download button allows them to fetch an updated copy of the repo (if available).
+
+![JupyterLab Gallery tile on hover to update repo](/img/how-tos/jupyter-gallery-tile-update.png)
+
+## Conclusion
+
+For more information on the JupyterLab-Gallery project, visit the
+[JupyterLab-Gallery codebase repo](https://github.com/nebari-dev/jupyterlab-gallery).
+
+For more information about custom JupyterLab Overrides in the Nebari config, visit the [Custom Overrides Configurations](../explanations/custom-overrides-configuration#jupyterlab) documentation.

docs/docs/how-tos/jupyter-gallery.md

@@ -104,7 +104,7 @@ Be sure to fill in the following fields carefully:
     - The recommended minimum vCPU and memory for a `general` node is 8 vCPU / 32 GB RAM
     - The recommended minimum vCPU and memory for a `user` and `worker` node is 4 vCPU / 16 GB RAM
   - `Disk size`
-    - The recommended minimum is 200 GB for the attached EBS (block-strage)
+    - The recommended minimum is 200 GB for the attached EBS (block-storage)
 - "Node Group scaling configuration"
   - `Minimum size` and `Maximum size` of 1 for the `general` node group
 - "Node Group subnet configuration"