# Bi-weekly Nebari community meeting | 13 Feb 2024 🪴💎

###### tags: community-meeting

**Meeting link: https://meet.google.com/rio-ngrj-kyh**
**Moderator: Chuck**
**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.

## Attendees

_All meeting attendees can add your details here!_

* Prefered name / pronouns (optional) / @github-handle / affiliation (optional)

## 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 ...]

* Chuck
* Tyler
* Johnny
* Ken
* Marcelo
* Dharhas
* Adam
* Dharhas
* Pavithra
* Kim
* Mike
* Chima (Prince)

### New members to be added to `nebari-dev`?

* TBD

## Updates and announcements

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

* Gracefully archiving jhub-client: https://github.com/Quansight/jhub-client/issues/22

## 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. :)_

* Next Release
* conda store RC is comming soon
* Marcelo will be the release captain
* Some PRs need to be included: #2214 is nice to have
* Scaling to zero needs to be tested
* Release process:
* Dharhas: Time-based release is tricky because of resourcing
* Kim: TIme-based let's users knows when the next release is
* Chuck: If the release process is easy, we can quicly make small releases. Which also gives us practice
* Mike: Quick releases also let's us fix security vulnerabilitites
* Chuck: We need confidence in the stability of `develop`
* **Final - Don't have a strict schedule but generally try to do more releases. A rough timeline to hold ourselves to is: quartely-cadence.**
* Nebari and docker images are coupled right now, but can be overridden
* Mike: We may have to update the docker images with new versions of dependencies soon
* Working processes:
* Include release planning and progress in the community meeting
* Review exisiting plan, ask for community input on priorities
* Marcelo:
* A conda-store instability
* SciPy proposal - several Nebari proposals creates conflicts, so let's only submit one
* Dharhas: JHub Apps is a good topic
* Dharhas - We're deploying Nebari for conf tutorials

## Actions

_Clear action items with an assignee._

- [ ] Pavithra - Update the release process docs & inlcude the working process
- [ ] Marcelo - Create a discussion about the conda-store pod failure