I feel a single list is okay for now, given we are in early stages.. After more reflection,
- I think the main gap with discussing issues over mailing list is ease of pasting code/stacktraces. I think we can recommend gists for this? (if this is addressed, then what we have is good enough) - Will anyway create a thread on ML for folks who keep filing GitHub support issues, to have visibility/discoverability. dev@ please encourage such users to engage on the mailing list for support issues going forward (I think some of us are doing this already) Thanks Vinoth On Wed, Mar 6, 2019 at 8:18 AM Thomas Weise <[email protected]> wrote: > It sounds like there are support type of questions that need an appropriate > channel. > > Many projects have a user@ list for such questions and some use the ASF > slack also. Both may be better suited for discussion and the lists are > better for discoverability. > > > On Tue, Mar 5, 2019, 6:25 PM Vinoth Chandar <[email protected]> wrote: > > > All, > > > > I have moved all valid GitHub issues over to JIRA. From now on, this > > becomes the source of truth for all development bugs. > > https://issues.apache.org/jira/projects/HUDI/issues/ > > > > There are some pending GitHub issues, which are (almost) all user support > > related > > https://github.com/uber/hudi/issues > > > > How does everyone feel about > > > > - Continuing to use Github Issues are a complimentary support channel? > > Benefits I see : Unclutters jira, GH is easy to share code/stacktrace, > > lower friction to engage (GitHub account is sufficient to report) > > - User support questions always start on dev@ ML as today. If sharing of > > stack trace etc is needed, gists/issues can be used > > - We will create a dev@ thread for each support issue opened on GH and > > encourage reportee/commentors to discuss on ML. > > - Real issues then graduate into JIRA as bugs/features, HIPs etc.. > > > > (If we are in agreement, I will update the community page) > > > > Thanks > > Vinoth > > > > On Tue, Mar 5, 2019 at 2:15 PM Vinoth Chandar <[email protected]> wrote: > > > > > I am planning to work on it, this week.. Contributors are still > creating > > > GH issues atm. > > > Want to add better docs for signing up on ASF Infra and getting them > > moved > > > over. > > > > > > On Tue, Mar 5, 2019 at 1:53 PM Thomas Weise <[email protected]> wrote: > > > > > >> You are right, folks need to be added to the roles. > > >> > > >> Also other contributors will need to be added before they can be > > assigned > > >> issues. > > >> > > >> On Tue, Mar 5, 2019 at 1:46 PM Vinoth Chandar <[email protected]> > > wrote: > > >> > > >> > Balaji was unable to assign JIRAs to himself before. Once I added > him > > to > > >> > PMC role, he is able to. > > >> > Thought everyone would have the same issue. > > >> > > > >> > Nishith, add you just now. > > >> > > > >> > > > >> > On Tue, Mar 5, 2019 at 1:41 PM Thomas Weise <[email protected]> wrote: > > >> > > > >> > > JIRA should already be setup so that PPMC members have the > required > > >> > > permissions. > > >> > > > > >> > > Any specific issue you encounter? > > >> > > > > >> > > > > >> > > On Tue, Mar 5, 2019 at 1:39 PM nishith agarwal < > [email protected] > > > > > >> > > wrote: > > >> > > > > >> > > > My JIRA ID : *nishith29* > > >> > > > > > >> > > > -Nishith > > >> > > > > > >> > > > On Tue, Mar 5, 2019 at 1:36 PM Vinoth Chandar < > [email protected]> > > >> > wrote: > > >> > > > > > >> > > > > I just started on setting up more things on JIRA.. > > >> > > > > > > >> > > > > Can PMC members respond with your jira id, so I can setup > perms > > >> > > > correctly? > > >> > > > > > > >> > > > > Thanks > > >> > > > > Vinoth > > >> > > > > > > >> > > > > > >> > > > > >> > > > >> > > > > > >
