GITHUB plus GIT VS JIRA plus GIT

Introduction

In dev ML at https://lists.apache.org/thread.html/r0e44a477ab39efa2b5d4c8816b67d381864a7bf60728d2915531e926%40%3Cdev.ofbiz.apache.org%3E we started a discussion about Pro and Cons with GH (GitHub)+Git and Jira+Git.

This page is intended to capture the pros and cons regarding each for the project.

Positive aspects of Github+Git versus JIRA+Git

Github + Git

JIRA + Git

Tight integration between Github and Git
More known among developers
Simple merge workflow (1 push button)
Intrinsic tools available to version & release (git aspect)
Enables developers in an easy way (forking/development collaborations)

More known in the enterprise world
Success story for many projects of the ASF
Lots of defined dashboards/overviews/etc. to provide insights to (potential) adopters and contributors
Well defined integration between JIRA and Git
Well defined separations of functions between JIRA and Git
Project can define own fields/workflow (JIRA)
Current setup of JIRA enables non-privileged contributors to participate in workflows (i.e take control to move forward, etc.)

Negative aspects of Github+Git versus JIRA+GIT

Github + Git	JIRA + Git
Less suited for project management reports (lack of dashboards etc per current setup of the report - Not easy for potential adopters to get a feel of the project) INFRA is required for every workflow change to GITHUB requires additional plugins to do stuff (ref #4) Legacy tools need to be kept (for history sake, etc.) Current setup only favours privileged contributors to participate in workflows.	Loosely coupled integration between JIRA+GIT

Questions and Answers

Things to check and clarify.

Question

Answer

1. What will be the process to give permissions to contributors on GitHub after they have filed their ICLA?

see https://ofbiz.apache.org/getting-involved.html

(Jacques Le Roux )Anybody should be allowed to create issues (see point 3 below).

(Michael Brohl ): yes, but not anyone can provide patches afaik. They must file an ICLA first and then get specific permissions.

Then comes SPAM and how to handle it. Here are 2 answers:
https://help.github.com/en/github/building-a-strong-community/reporting-abuse-or-spam
https://github.com/marketplace/actions/mark-as-spam

2. How do we control the permissions for committers and contributors on GitHub?

(Jacques Le Roux )Same than point 1. It's open, like in GH you can also have SPAM in Jira once you have created an account...

(Michael Brohl ) we have fine grained permissions set in Jira, the answer does not refer to that.

3. What do we offer for contributors who are not able or willing to maintain their own repositories and follow the PR process?

It is relatively easy to clone the official repo, change and create a patch through git diff but it might be a hurdle for people to take all necessary steps for the PR process.

(Jacques Le Roux ) This was already answered with the point 3. We should ask Infra to offer the "Issues" feature (a top button) in our GH mirrors.

You can then report in GH as you would to in Jira. It mostly offers the same possibilities than Jira. I guess it's not a problem for Infra to open the feature, but that needs to be confirmed

4. When we publish a new release we update Jira versions to reflect the change. This information is useful to group Jira tickets by version. Is there a similar feature in GitHub?

(Jacques Le Roux ) Is the point 4 not answering this question? Also see related Jacopo's answer in my comment below

(Michael Brohl ) this is not answered as long as the process is clear. How is it used in practice?

5. Has GitHub tools alike elaborated search in Jira, e.g. with filters? Can existing filters/views be migrated from Jira to GitHub?

Examples for filters:

all open issues
all open issues assigned to me (or specified user)
all open issues with a patch (or then PR)
all issues watched by me
all issues reported by x, y, z
etc., see Jira search capabilities.

(Jacques Le Roux ) Incidently, I made a seach in Jira yesterday. I was looking for "Canonical url". I could not find a result, but Markmail allowed me to find it:

Jira:

type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
JQL and issue key arguments for this macro require at least one Jira application link to be configured

Markmail:

https://ofbiz.markmail.org/search/?q=%22Canonical+url%22

So, though I very like Jira search because it can be right to the point, but it's not always accurate. I can then trust Markmail, which is easier to use than Pony when you are lazy. Because it searches on all MLs for all time and you can then filter by many ways. It's also still very fast.

(Michael Brohl ) I am able to find 4 results for "canonical url" and even more with using "canonical". You should use the search correctly.

(Jacques Le Roux ) Can you please share your research or a filter? Mine was <<project = OFBIZ AND status in (Open, "In Progress", Reopened) AND text ~ "\"Canonical url\"">>

Part of your markmail results are from the users list which has nothing to do with Jira.

(Jacques Le Roux ) yes MarkMail searches are wide. Most of the time you need to filter after.

This answer is also simplifying the answer to one specific search term which does not qualify the search. And without similar tests of the GitHub search this finding is useless. You should remove this answer.

(Jacques Le Roux ) It was only to illustrate my point. As I said I "very like Jira search" and know a bit about it

I'll enhance the question to be more clear what I mean with search functions/filters.

Space shortcuts

Child pages

Positive aspects of Github+Git versus JIRA+Git

Negative aspects of Github+Git versus JIRA+GIT

Questions and Answers

References