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...... > >>> > > >
