Yes, I'm on this!
First question, what is a [DISCUSS]? :) I assume you are talking about a dev@ thread with that label to discuss this
possibility, but is there more to it than that?
As I understand it now, "it" is changing from our current setup, in which we act against Apache git and the results are
mirrored to Github, to the opposite direction, in which we act against Github and the results are mirrored to Apache
git. As far as PR machinery goes, an advantage that I see is that we will be able to use the complete excellent web UI
at Github. Right now, we can comment, review, etc, but when it comes time to merge, it occurs via CLI. It's true that
that isn't the end of the world, but is both clunky (as Andy notes) and error-prone (I had a annoying problem with it on
a recent PR). We would also get accurate results from Github's visualization tools, which isn't a major thing, but could
be nice.
My understanding is that such a change will have no effect at all on our current JIRA integration, but I will get that
confirmed (or disproved!) by INFRA. Going to Github issues would be a different choice, and I am not arguing for that
now. (Trying to split as much off of this as possible to keep the decision simpler!)
Bruno-- if it's not obvious, I am intentionally splitting off the question of where we maintain our site, which is a
really good thing to discuss, but think it is orthogonal.
ajs6f
Andy Seaborne wrote on 11/11/17 10:41 AM:
On 09/11/17 18:24, aj...@apache.org wrote:
Great, thanks!
So folks, is there interest in pursuing this rearrangement of our source
management? I would certainly vote for it.
Great - do you want to take this on and see us through the process?
We'll need a [DISCUSS] I expect to make sure we all know what the VOTE is really about.
I'm not clear what "it" is exactly.
I'm all linked up - 2FA etc, and it can see which repo I have access to.
I use JIRA search and git history more and more to understand what users are
asking about and to trace down bugs.
How does gitbox interact with JIRA? Do we get a nice set of JIRA comment
(obvious existing bug - JIRA isn't markdown so
`` and {{}} mess up.
I guess discussion is on GH issues, not JIRA tickets, which is a change but
fine by me.
The "git pull github pull/XXX/head --no-ff ; git push" is clunky but not the
end of the world.
(Unrelated wish - delete of the local branch - is that "git fetch --prune"?).
it's not possible to use the Github PR review machinery transparently
This confused me - we use GH PR review at the monent. Could you expand the
point?
So I guess I want to know what changes in the workflows for submission (nothing
presumably but what about JIRA? Auto
create-JIRA-on-PR would be fancy) and for acceptance
I'm expecting changes if we go "gitbox" and that's fine, I'm not arguing for
the status quo. It's not easy to reverse so
I want to know what it is.
Andy
https://github.com/apache/jena/blob/master/CONTRIBUTING.md
ajs6f
Daniel Pono Takamori wrote on 11/9/17 1:22 PM:
Gitbox would indeed allow you to have the Github tools available to
committers. It treats Github as the canonical source (we also keep a
copy on Gitbox), which allows the PRs and issues to be a bit more
convenient (there are still some things we can't support due to the
Github's coarse permission structure).
We require all committers to use Github's 2FA [0] so once you have a
taken a vote in the project, file a ticket on the INFRA JIRA [1] and
then your committers can run through the Gitbox syncing [2] to matchup
ASF IDs and Github IDs.
Let us know if you have any other questions.
[0] - https://help.github.com/articles/providing-your-2fa-authentication-code/
[1] - https://issues.apache.org/jira/browse/INFRA
[2] - https://gitbox.apache.org/setup/
On Thu, Nov 9, 2017 at 10:50 AM, <aj...@apache.org> wrote:
Hi, I'm a committer for Jena. Recently, we had some discussion about our
source management and there was some uncertainty about how we can arrange
the relationship between Github and Apache git.
Currently, commits go against Apache git, and Github picks them up and
mirrors them, which is a bit annoying in that it's not possible to use the
Github PR review machinery transparently. This is not a big deal, but is it
in fact possible to do that? In other words, is it possible to (e.g.) merge
PRs at Github and have Apache git pick up the change?
I went to https://gitbox.apache.org/setup/ and linked my accounts, but that
didn't seem to do anything...
Thanks for any info!
--
ajs6f
