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

Reply via email to