Hi

I am exploring xtable for understanding . Shall we join this meeting also ,
if I could learn from this as well .


Thanks

On Wed, Mar 20, 2024, 3:04 AM Ashvin A <ash...@apache.org> wrote:

> Hello Community,
>
> The recording of our first community meeting is now on our new YouTube
> channel!
> Watch Here: Apache XTable Community Meeting #1
> <https://www.youtube.com/watch?v=HjNk_naj-Lk>
>
>
> https://www.youtube.com/@ApacheXTable
>
> Our project now has its own dedicated channel. Please subscribe and stay
> updated on future community meetings, demos, tutorials, and discussions. To
> ensure smooth content management, I propose adding all committers as
> channel managers. This will allow them to handle permissions, create, edit,
> and delete content.
>
> Please share your thoughts on this approach.
>
> Best,
> Ashvin
>
>
> On Thu, Mar 14, 2024 at 6:00 AM Jean-Baptiste Onofré <j...@nanthrax.net>
> wrote:
>
> > Hi guys,
> >
> > I'm very sorry, I missed this meeting due to conflict.
> >
> > I will join the next one.
> >
> > Regards
> > JB
> >
> > On Thu, Mar 14, 2024 at 7:38 AM Ashvin A <ash...@apache.org> wrote:
> > >
> > > Hello all,
> > >
> > > Thanks to everyone who was able to join the community meeting on March
> > 11.
> > > The discussion was lively and productive, and I appreciate everyone's
> > > contributions.
> > >
> > > Below you'll find an auto-generated summary of the meeting. As a
> > follow-up,
> > > I am planning to start discussion threads and create issues. One of
> these
> > > will be to share the meeting recording and the meeting transcript. I
> hope
> > > that this will provide a valuable resource for those who were unable to
> > > attend.
> > >
> > > Once again, thank you for your participation.
> > >
> > > Best,
> > > Ashvin
> > >
> > > ====
> > > Start time 3/11/24, 7:52:14 AM
> > > End time 3/11/24, 8:57:46 AM
> > >
> > > Participants
> > >
> > >    1. Albert Wong
> > >    2. Ashvin Agrawal
> > >    3. Dipankar
> > >    4. Ismael Mejía Useche
> > >    5. Jesus Camacho Rodriguez
> > >    6. Kyle
> > >    7. Stamatis Zampetakis
> > >    8. Tim Brown
> > >    9. Vinoth Chandar
> > >
> > > ====
> > > *Notes Generated by Copilot.*
> > > *Key Topics:*
> > >
> > >    - *First release:* The members advised that the first release is a
> > major
> > >    milestone for the project and suggested some tasks to prepare for
> it,
> > such
> > >    as adding license headers, checking dependencies, renaming classes,
> > and
> > >    automating the release process.
> > >    - *Renaming classes:* The participants agreed that it is better to
> > >    rename the classes that have the "One" prefix to avoid confusion and
> > API
> > >    breakage in the future, and decided to start a discussion thread on
> > GitHub
> > >    to solicit feedback and suggestions from the community.
> > >    - *Community page on the website:* Kyle volunteered to create a
> > >    community page on the website that would have links to the dev
> mailing
> > >    list, GitHub, Slack, and the community meeting schedule and agenda.
> > >    - *Wiki:* The participants discussed the pros and cons of having a
> > wiki
> > >    for the project, and decided to avoid adding another tool for
> > communication
> > >    and instead use the dev mailing list, GitHub discussions, and Google
> > Docs
> > >    for design discussions and collaboration, and the website for final
> > >    documentation.
> > >    - *Squash and merge:* The participants discussed the issue of squash
> > and
> > >    merge when committing PRs, and agreed that the committers should
> > either
> > >    squash the commits themselves or request the author to do so before
> > >    merging, and also document the contribution guidelines for the
> > project.
> > >    - *CI:* Jesus explained the current CI setup using Azure pipelines
> and
> > >    GitHub actions, and the challenges and complexities of using a
> mirror
> > repo
> > >    and a bot. Vinoth shared his experience with Hudi and suggested
> > evaluating
> > >    the budget and resources available for GitHub workflows. The
> > participants
> > >    agreed to discuss this further on the dev mailing list and find a
> more
> > >    streamlined solution.
> >
>

Reply via email to