+1 to prioritize newcomers. +1 to timeboxing Cheers, Dmitri.
On Tue, Apr 15, 2025 at 1:55 PM Russell Spitzer <russell.spit...@gmail.com> wrote: > I'm strongly in favor of having a timeboxed Agenda. I do want to make sure > we always poll new attendees first. I'm not sure this would fit into our > agenda but the Parquet sync usually does a roll-call and "what are you > interested in?" at the top of the hour. We probably have too many people > for that but a "hello i'm new and I'm hear for ..." is probably great for > first timers. > > I also want to keep debates out of the meeting. If folks have a lot of > questions we should just punt to a sub-meeting or mail thread. > > On Tue, Apr 15, 2025 at 2:17 AM Jean-Baptiste Onofré <j...@nanthrax.net> > wrote: > > > Hi folks, > > > > In order to "structure" on Community Meetings, I propose to have the > > following plan for the meetings, organized by themes: > > > > 1. Highlights (5mn): > > all cool things we did during the last two weeks > > 2. Podling Governance (5/10mn): > > Update about release, new committers, incubator report, security > > reports, ... > > 3. UX and Onboarding (5/10mn): > > Update about user experience (UI, CLI, ...) and user onboarding > > (documentation, examples, ...) > > 4. Persistence (5/10mn): > > Update about persistence API, new backends, ... > > 5. Security and Data Governance (5/10mn): > > Update about security and data governance layer (SSO, RBAC, FGAC, > > ABAC, ...), integration with IdP, ... > > 6. Catalog Integration (5/10mn): > > Update about Catalog Federation, Foreign Tables, Table Formats > > Support/Converter, Unity integration, ... > > 7. Polaris Tools (5/10mn): > > Update about Polaris tool (catalog migrator; benchmark, ...) > > > > The idea is to populate each theme before the meeting to focus on key > > topics to discuss during the meeting. > > > > Thoughts ? > > > > Regards > > JB > > >
