OK, I just asked on #asfinfra whether there are any requirements from the ASF for keeping the bot and Daniel Gruno responded:
> [5:58 PM] Daniel Gruno (humbedooh): you don't need a JIRA copy if you > don't want it > [5:59 PM] Daniel Gruno (humbedooh): or you can just have it appended > to the worklog > [6:04 PM] Daniel Gruno (humbedooh): from our side of the pond, as long > as one copy of the discussion hits the ML, we're good > [6:05 PM] Daniel Gruno (humbedooh): worklog is a workaround where it > hits JIRA without sending an email to the ML So, we can decide on our own whether we want to disable it or we could also us this workload as a comprise, although I don't know if that provides much value for us. I'm personally in favor of simply disabling this bot. We would still get everything on the dev list and everyone can read the original comments on GitHub. Should we wait 72h in case someone has good arguments for keeping everything as is? Am 08.10.2018 um 17:54 schrieb Stephen Mallette: > i tend to find it distracting myself. not sure about anyone else. also not > sure if it's an option to change, but i guess i'd be in favor of disabling > that portion of the integration if it could be. > > On Mon, Oct 8, 2018 at 11:51 AM Florian Hockmann <[email protected]> > wrote: > >> If the only requirement from the ASF is that everything ends up on the >> mailing list, then that should already be met by GitBox which sends us >> the comments via mail. The additional bot only creates them as comments >> on JIRA issues which are then sent again via mail from JIRA. >> So, I don't see where we might miss anything on the mailing list if we >> simply disable the copying of GitHub comments into JIRA issues. GitHub >> comments that aren't linked to a JIRA issue still end up on dev through >> BitBox. We only lose the comments in JIRA. But does anyone actually want >> to read comments in JIRA that are copied over from GitHub? >> >> Am 08.10.2018 um 17:28 schrieb Stephen Mallette: >>> That's an interesting tangle - ultimately, Apache requires those comments >>> to end up here on the mailing list and I wonder if that's just >> unavoidable. >>> Like we get the copy from GitHub to dev and then it also has to post to >>> JIRA which then notifies dev too. I guess the issue is that GitHub >> comments >>> don't always tie to JIRA and perhaps the automation isn't smart enough to >>> differentiate that. You could ask about it on #infra i guess or if gruno >> is >>> still following the thread, perhaps he'll comment. >>> >>> On Mon, Oct 8, 2018 at 11:22 AM Florian Hockmann <[email protected] >>> >>> wrote: >>> >>>> Can't we now also disable the ASF GitHub Bot that copies all PR comments >>>> to the linked JIRA issue since GitBox already sends us those comments >>>> via this mailing list? Would be great if we wouldn't get each comment in >>>> two separate mails anymore. Or do we really want to have all comments >>>> also in JIRA? >>>> >>>> Am 08.10.2018 um 17:07 schrieb Stephen Mallette: >>>>> Note that I've asked Infra to shut off GitHub issues/projects since >> we're >>>>> not using them. It's crazy how fast people started using that once it >> was >>>>> enable.....like people were just sitting on their keyboards waiting to >>>>> create issues. crazy >>>>> >>>>> On Sat, Oct 6, 2018 at 11:10 AM Daniel Gruno <[email protected]> >>>> wrote: >>>>>> And this has now been done. >>>>>> Y'all should visit https://gitbox.apache.org/ and click on the 'Link >>>>>> GitHub and ASF accounts' thing and link your ASF accounts so you can >> get >>>>>> write access to github. >>>>>> >>>>>> You may use the following new URLs for the tinkerpop repo: >>>>>> - https://gitbox.apache.org/repos/asf/tinkerpop.git >>>>>> - [email protected]:apache/tinkerpop.git >>>>>> >>>>>> With regards, >>>>>> Daniel. >>>>>> >>>>>> On 2018/10/05 14:14:48, Stephen Mallette <[email protected]> >> wrote: >>>>>>> After some problems with pushes to Apache Git (weird slowness and >>>>>>> "demultiplexer" problems) I contacted Apache Infra. In the midst of >>>>>> working >>>>>>> things through with Daniel Gruno he asked again if we'd like to go to >>>>>>> GitBox. Well, after a few IM exchanges, I learned that there's even >>>> less >>>>>>> change and impact to the community than we thought to make this move. >>>>>>> Basically, they just give us write access to the existing GitHub >>>>>>> repo.....................ugh (wish i'd understood that a long time >>>> ago). >>>>>>> Anyway, as there were no objections in the past to making this move >> and >>>>>> we >>>>>>> were just looking for the right time to do it, I went ahead and >> created >>>>>>> this: >>>>>>> >>>>>>> https://issues.apache.org/jira/browse/INFRA-17109 >>>>>>> >>>>>>> Let's get it done...... >>>>>>> >>>> >> >>
