Try   HackMD

Bi-weekly Nebari community meeting | 25 April 2023 🪴💎

tags: community-meeting

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

Welcome to the Nebari community meeting!

Guidelines

  • This meeting is covered by Nebari's Code of Conduct.
  • 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.
  • (Not implemented yet) We use takingnotes.rocks to randomly select a meeting moderator and note taker at the beginning of each meeting. We'll make sure to select returning members, as to not put new community members 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 after the meeting for better searchability.

Attendees

All meeting attendees can add your details here!

  • Prefered name / pronouns (optional) / @github-handle / affiliation (optional)
  • Pavithra / she-her / @pavithraes / Quansight
  • Eskild / he-him / @iameskild / Quansight
  • Kim / @kcpevey / Quansight
  • Adam Lewis / @Adam-D-Lewis / Quansight
  • Vinicius / @viniciusdc / Quansight
  • Maxime / @Dr0p42 / NaasAI
  • Rich Signell / @rsignell-usgs /
  • Dharhas Pothina / @dharhas / Quansight
  • Johnny Bouder / @jbouder / 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 comfortable sharing. :)

[Quick intro: Hi, I'm ..! I live in …, and study … / work as a … at … I'm a Nebari user/contributor/maintainer, and I'm primarily 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!

  • Dharhas, PyCon updates you'd like to share with everyone?
    • Impromptu demos of Nebari and conda-store 6-8 times a day
    • 2 new contributors created PRs as a part of mentored sprint
      • Some issues, noted action items
    • Tutorial went well, major issues with dask-gateway. Ref: https://github.com/nebari-dev/nebari/issues/1750
  • Rich will be presenting a tutorial on 10th May
  • [Adam] Nebari Workflow Controller PR (https://github.com/nebari-dev/nebari/pull/1741)
    • k8s admission controller that prevents users from mounting volumes and conda envs they shouldn't have access to when using argo workflows
    • Can be extended with a similar mutating admission controller to give a simple default experience for users of Argo Workflows
  • [Eskild] Prioritzing upgrading (max) Kubernetes version
    • Azure and DO no longer support Kubernetes version 1.23.
    • Will be working with Adam
    • what is the typical cloud-k8s cycle?
      • every 3-6 months upgrade, supported for ~2 years
      • document this in the maintainers guide -> release process

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 would be a place to ask. :)

  • Maintenance processes:

    • Community bi-weekly triage meetings? Maybe rotate the lead?
    • Align on contributing workflow
      • new-contributor kubernetes test issue
  • RFDs?

  • [Johnny] updates on cds dashbords?

    • In talks with DTN about replacing cds dashboards with somethign else
    • we can get a demo working soon
    • Johnny might be able to support this effort
  • [Dharhas] working on a gov project in collab with metrostar

  • [Rich] working with planetary computer

    • Tom Augsperger might take a look at Nebari
    • Azure/k8s issue, ping Tom about this

Actions

Clear action items with an assignee.

  • Assignee - Action item
  • Pavithra - create an issue about conda-build req for local test
  • Pavithra – look into issue templates for the docs repo

Did we complete last meeting's actions?

(Note taker to copy past action items here)