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

Reply via email to