For OpenNLP, I created a ticket for INFRA, but most of the interaction happened
via Hipchat + e-mails, but it was Joern who contacted them.
https://www.apache.org/dev/infra-contact#how
I tried accessing Hipchat with little luck in the past. Don't remember if it
was my account type, or apache e-mail, that didn't work...
But probably Hipchat is the best option.
HTH
Bruno
From: ajs6f <[email protected]>
To: [email protected]
Sent: Tuesday, 19 December 2017 3:53 AM
Subject: Re: Jira and Gitbox integration?
Nope. I have not been able to find out anything more about this, and INFRA
never answered my last email. I agree that the current workflow is not terrible
at all. I do think going the other way might be a little better, but as you
say, it's a question of balance. I think the most interesting aspect would be
lowering the bar to small (one-commit-ish) contributions as low as possible. I
would like to think we might get more contribution that way, but I don't claim
to be sure about that.
As an not-very-experienced Apache-er, I probably should have asked this a while
ago, but is there a protocol about bugging INFRA? If an email goes unanswered
for several weeks, better to email again or better to file a ticket on INFRA
asking for info?
ajs6f
> On Dec 17, 2017, at 11:28 AM, Andy Seaborne <[email protected]> wrote:
>
> Any news?
>
> Even after reading around, I still don't know how JIRA fits in (if at all).
> It might only send emails c.f commits@.
>
> A github only flow is fine by me. Loosing JIRA will be a bump but it is a
> question of balance - more GH input vs undoing what we have talked about for
> some time (JIRA). or we have to run both nodes (not so different).
>
> e.g.
> http://opennlp.apache.org/using-git.html
>
> Any other good links?
>
> (there is more that we can do with the contribution process like ask for
> one-commit (mostly) contributions,
>
> Of course, all this takes time to do, like documentation.
>
> The current GH-mirror workflow isn't that problematic at the moment albeit it
> a few extra steps.
>
> (the main annoyance for me is deleting local branch and the gitbox does not
> change this one way of the other as far as I can see).
>
> Andy
>
> On 17/11/17 14:39, ajs6f wrote:
>> Hi, INFRA--
>> Here at Jena we are considering moving our Apache git <-> Github mirroring
>> to accept changes at Github and mirror them to Apache git (currently it's
>> the other way around). But right now we have some nice Jira integrations,
>> and so we have some questions about how that would work if we reversed the
>> mirroring.
>> Currently, any mention of a Jira ticket (e.g. "I think this could affect
>> JENA-1234") in a Github PR automatically copies the conversation for that PR
>> over to the comments in that Jira ticket. Will we be able to keep that
>> integration if we reverse the mirroring?
>> Github treats issues/tickets and PRs very similarly-- is it possible to
>> integrate Jira in a similar way so that a PR that doesn't mention an extant
>> particular Jira ticket automatically files a new Jira ticket?
>> Thanks for any info and all that you already do for us!
>> ajs6f
