+1 发件人: Jungtaek Lim <[email protected]> 日期: 2024年8月10日 星期六 07:12 收件人: Denny Lee <[email protected]> 抄送: bo yang <[email protected]>, Kent Yao <[email protected]>, "[email protected]" <[email protected]> 主题: [外部邮件] Re: [DISCUSS] Using Github Issues for Spark-Connect-Go _only_ issues.
+1, good size project for experiments and it’s not a one way door 2024년 8월 10일 (토) 오전 1:09, Denny Lee <[email protected]<mailto:[email protected]>>님이 작성: +1 (non-binding) to start as a small experiment On Fri, Aug 9, 2024 at 11:56 PM bo yang <[email protected]<mailto:[email protected]>> wrote: +1 to start small as an experiment to see how people use GitHub issue... On Thu, Aug 8, 2024 at 11:54 PM Kent Yao <[email protected]<mailto:[email protected]>> wrote: +1 On 2024/08/08 23:24:32 Hyukjin Kwon wrote: > SGTM > > On Thu, 8 Aug 2024 at 14:53, Martin Grund <[email protected]> > wrote: > > > Hi folks, > > > > I wanted to start a discussion for the following proposal: To make it > > easier for folks to contribute to the Spark Connect Go client, I was > > contemplating not requiring them to deal with two accounts (one for Jira) > > and one for Gihutb but allow using GitHub Issues for bugs and issues that > > are specific to *only* the Spark Connect Go client. > > > > Jira will still be used for issues that span core Spark. This allows us to > > easily label issues for starter tasks in one place, for example. > > > > I am explicitly not proposing to change the behavior for the main Spark > > repository; here, the existing procedure remains. > > > > What do you think? > > > > Martin > > > --------------------------------------------------------------------- To unsubscribe e-mail: [email protected]<mailto:[email protected]>
