..+1 to start small as an experiment to see how people use GitHub issues...
That may be an approach, My suggestion is an industry standard Proof of Concept (PoC) which is an accepted approach for testing the feasibility of using GitHub Issues for managing Spark Connect Go client issues. This is a follow-up with the early on discussion with the proposer @Martin Grund <mar...@databricks.com.invalid> By implementing a PoC, we can: 1. Assess the impact, evaluate how the change affects the development workflow and team collaboration. 2. Identify potential issues, uncover any challenges or limitations early in the process. 3. Gather feedback, collect input from the developer and contributors to refine the approach. 4. Minimize risk, test the new system in a controlled environment before full-scale adoption. Key steps for a successful PoC: 1. Define the scope: Clearly outline the specific issues or features to be managed using GitHub Issues during the PoC, which could be part of SPIP 2. Set up the environment: Configure GitHub Issues with the appropriate labels, milestones, and workflows. 3. Involve the team: Ensure team members are aware of the PoC and their roles in it. 4. Monitor and evaluate: Track key metrics and gather feedback throughout the PoC. HTH 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 *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 Fri, 9 Aug 2024 at 19:36, Denny Lee <denny.g....@gmail.com> wrote: > +1 (non-binding) to start as a small experiment > > On Fri, Aug 9, 2024 at 11:56 PM bo yang <bobyan...@gmail.com> 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 <y...@apache.org> wrote: >> >>> +1 >>> >>> On 2024/08/08 23:24:32 Hyukjin Kwon wrote: >>> > SGTM >>> > >>> > On Thu, 8 Aug 2024 at 14:53, Martin Grund >>> <mar...@databricks.com.invalid> >>> > 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: dev-unsubscr...@spark.apache.org >>> >>>
