# Bi-weekly Nebari community meeting | 9 May 2023 🪴💎

###### tags: community-meeting

**Meeting link: https://meet.google.com/rio-ngrj-kyh**
**Moderator: Dharhas**
**Notetaker: Pavithra**

Welcome to the Nebari community meeting!

## Guidelines

* This meeting is covered by [Nebari's Code of Conduct](https://github.com/nebari-dev/governance/blob/main/CODE_OF_CONDUCT.md).
* Please feel free to participate in open discussions, share your projects, or sit back and listen!
* When you'd like to speak in a discussion, use Google Meet's **"raise hand"** feature, and wait for the moderator to call your name.
* We use [takingnotes.rocks](https://takingnotes.rocks/) to **randomly select a meeting moderator and note taker** at the begining of each meeting. We'll make sure to select returning members, as to not put new community memebers on the spot. :)
* The moderator is responsible for running the meeting, and giving everyone a speaking opportunity
* The note taker is responsible for recording all important points in this HackMD document, **and** post it on the [GitHub Discussions forum](https://github.com/orgs/nebari-dev/discussions/categories/community-meetings) after the meeting for better searchability.

## Attendees

_All meeting attendees can add your details here!_

* Prefered name / pronouns (optional) / @github-handle / affiliation (optional)
* Vinicius / @viniciusdc / Quansight
* dharhas / @dharhas / quansight
* Adam / @Adam-D-Lewis / Quansight
* Kim / @kcpevey / Quansight
* Pavithra / @pavithraes / Quansight
* Maxime / @jubloum / NaasAI
* Philip / @pmeier / Quansight
* Johnny Bouder / @jbouder / MetroStar
* Scott Blair / MetroStar

## Introductions

_If you are new to this meeting, this is the time to introduce yourself!_
_We have an introduction template below, but please share what you're comfortbale sharing. :)_

[Quick intro: Hi, I'm ..! I live in ..., and study ... / work as a ... at .... I'm a Nebari user/contributor/maintianer, and I'm primarily i interested in .... In my spare time, I enjoy ...]

*

## Updates and announcements

_Share ongoing work, new releases, something cool you built on Nebari, upcoming conferences, and more!_

* Adam
* PR open to allow submitting an Argo Workflow with jupyterflow-override: 'true' tag and it'll populate the workflow with env vars, initContainers, etc. from the users jupyter user container.
* https://github.com/nebari-dev/nebari/pull/1741
* PRs to Update nebari upgrade instructions
* https://github.com/nebari-dev/nebari-docs/pull/329
* https://github.com/nebari-dev/nebari/pull/1794
* Worked on the Dask Gateway fix
* Release-related reviews
* Did a Nebari release a couple days ago:
* Fixes the Dask Gateway issue
* Ref: https://github.com/nebari-dev/nebari/blob/develop/RELEASE.md#release-202351---may-5-2023
* The latest release is available on conda-store now
* Follow up with setting this as part of the relase checklist and set this to be automatic on conda-forge side. [Tracking issue](https://github.com/nebari-dev/nebari/issues/1796)
* Vini:
* Reviewing older documentation PRs
* Waiting for follow-back: [#303](https://github.com/nebari-dev/nebari-docs/pull/303) [#280](https://github.com/nebari-dev/nebari-docs/pull/280)
* Experimenting with upgrading Keycloak -- haven't tested with a deployment
* Will test on AWS as I also want to double check the migration docs for upgrading Nebari (Qhub -> Nebari)
* Explored upgrading Dask Gateway to the latest version, and this seems to be working well. Pontentially availble in the next release
* Chris:
* Making conda-store more robust, adding more tests, bug fixes
* Note that Docker image building on conda-store in broken right now
* Philip:
* PR to make Nebari internals private
* Blocked on permissions to run all the tests
* Expect conflicts on open PRs, but git should handle it -- ping Phlip if it causes issues
* Wait to make the schema public
* Kim:
* Playwright PR is close - reviewed by Chris
* API docs PRs
* Pavithra:
* At JupyterCon: Nebari-adjacent talk on Friday, Nebari sprints

## Discussion topics

_Is there something we should discuss as a group? Something you want feedback on?_

_Note: If you have a usage question, our [Discussion Forum](https://github.com/orgs/nebari-dev/discussions) would be a place to ask. :)_

* Describe how to update Nebari to 2023.5.1 release (requires `nebari upgrade -c nebari-config.yaml`)

* CDS Dashboards updates?
* It'll be better to re-write the dashboard sharing mechanism
* Looking for funding or dev-resources

* Custom images RFD: https://github.com/nebari-dev/governance/issues/22
* Counter-proposal -- use conda-store to manage the base jupyterlab
* List of "base envs" similar too "selct profile" on the launch page
* Chris to update the issue with notes from today's chat

* Argo-workflows related RFDs:
* User Friendly Method for Jupyter users to run an Argo Workflow: https://github.com/nebari-dev/governance/issues/33
* Ways to Limit Argo Workflows Permissions - Mounting Volumes: https://github.com/nebari-dev/governance/issues/36

* Scoped Juputer Scheduler integration, ~15hrs of work

* RFD - Bitnami retention policy considerations: https://github.com/nebari-dev/governance/issues/21
* Discuss next week

## Actions

_Clear action items with an assignee._

- [x] Vini - Create an issue to track automating Nebari on conda-forge
- Everyone - review and update open PRs

Did we complete last meeting's actions?

(Note taker, please copy past action items here)