+1 (non-binding) On Mon, Aug 12, 2024 at 12:11 PM Denny Lee <denny.g....@gmail.com> wrote:
> +1 (non-binding) > > On Mon, Aug 12, 2024 at 16:43 Reynold Xin <r...@databricks.com.invalid> > wrote: > >> +1 >> >> On Mon, Aug 12, 2024 at 10:28 AM Mich Talebzadeh < >> mich.talebza...@gmail.com> wrote: >> >>> +1 for me >>> >>> Mich Talebzadeh, >>> >>> Architect | Data Engineer | Data Science | Financial Crime >>> PhD <https://en.wikipedia.org/wiki/Doctor_of_Philosophy> Imperial >>> College London <https://en.wikipedia.org/wiki/Imperial_College_London> >>> London, United Kingdom >>> >>> >>> view my Linkedin profile >>> <https://www.linkedin.com/in/mich-talebzadeh-ph-d-5205b2/> >>> >>> >>> https://en.everybodywiki.com/Mich_Talebzadeh >>> >>> >>> >>> *Disclaimer:* The information provided is correct to the best of my >>> knowledge but of course cannot be guaranteed . It is essential to note >>> that, as with any advice, quote "one test result is worth one-thousand >>> expert opinions (Werner >>> <https://en.wikipedia.org/wiki/Wernher_von_Braun>Von Braun >>> <https://en.wikipedia.org/wiki/Wernher_von_Braun>)". >>> >>> >>> On Mon, 12 Aug 2024 at 09:16, Martin Grund <mar...@databricks.com.invalid> >>> wrote: >>> >>>> Hi Folks, >>>> >>>> following the discussion in the previous thread, I would like to open >>>> the vote on the following proposal: >>>> >>>> Enabling the use of GitHub Issues for issue tracking for the Spark >>>> Connect Go repository. This will support the tracking of issues that are >>>> exclusively relevant to this project. For all issues that are cross-cutting >>>> with PySpark / Spark Core, regular Jira will be used. After 3-6 months, I >>>> will report back to the community about how the experience was and the >>>> lessons learned. >>>> >>>> I will start the vote with my +1. >>>> >>>> Martin >>>> >>>
