It’s pretty easy - just do a fork into your private repo, apply your code and create a pull request. After the check have passed, and the review process was positive, we merge. No need to create a dedicated branch, we cut a release branch from current main.
Cheers, —Alex > On 16. Apr 2023, at 13:03, Kristian Reitzel <[email protected]> wrote: > > Great! > > How do you prefer the git organisation? I assume we should create a new > branch from main(?). If so, is there any naming convention that we should > follow or other things that we should be aware of? This is our first > contribution to open source projects. > > Best, > Kristian > ________________________________ > Fra: Alexander Alten <[email protected]> > Sendt: søndag, april 16, 2023 11:22 AM > Til: [email protected] <[email protected]> > Cc: Michelle Sackmann Jensen <[email protected]> > Emne: Re: Status on SQL API > > Hey Michelle and Kristian, > > Awesome, and we just merged the initial contribution from Kausthub into the > main branch. Ready to go! > > Best, > —Alex > > — > Alexander Alten > PPMC Apache Wayang > [email protected] > > @apachewayang > >> On 15. Apr 2023, at 21:49, Kristian Reitzel <[email protected]> wrote: >> >> Hi Wayang Dev! >> >> Just a quick update on the research project involving the SQL API that >> Michelle and I are working on: >> >> Due to our limited time, we are focusing on implementing: >> >> 1. The join operator (probably just the inner join) >> 2. Sql query from both a csv and postgres data source >> >> We’re currently waiting for the current SQL API to be merged into the Wayang >> repository. Afterwards we will be happy to contribute with our work. >> >> We have been searching for the implementation of the join operator in the >> java API, but we haven’t succeeded. So if any of you have a pointer to this, >> it would be much appreciated! >> >> Best regards, >> Michelle and Kristian! > > > -- > databloom AI, Inc. > > 3401 N. MIAMI AVE. STE 230 > 33127 Miami, Florida > United States > > > -- Please consider the environment before printing this > email -- > > > > Disclaimer: > The content of this message is confidential. If you > have received it by mistake, please inform us by an email reply and then > delete the message. It is forbidden to copy, forward, or in any way reveal > the contents of this message to anyone. The integrity and security of this > email cannot be guaranteed over the Internet. Therefore, the sender will > not be held liable for any damage caused by the message. > -- databloom AI, Inc. 3401 N. MIAMI AVE. STE 230 33127 Miami, Florida United States -- Please consider the environment before printing this email -- Disclaimer: The content of this message is confidential. If you have received it by mistake, please inform us by an email reply and then delete the message. It is forbidden to copy, forward, or in any way reveal the contents of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet. Therefore, the sender will not be held liable for any damage caused by the message.
