Issues in github


(Pablo Hernandez-Cerdan) #1

What is the status on allowing opening issues in the github mirror https://github.com/InsightSoftwareConsortium/ITK?

I have some really minor warnings I find building tests, and an issue in github would be better than report it here. I still have problems logging into https://insightsoftwareconsortium.atlassian.net/secure/Dashboard.jspa, as I guess any new user not registered in the server.

Thanks!


GitHub issue labels
How to report ITK issues
(Andras Lasso) #2

Using Github for issue tracking would be very community-friendly: people would not have to create yet another account (by the way, I still cannot do anything on Jira) or need to learn how to use a new issue tracker (that most likely they would very rarely use).

We would also benefit from the integration between repository and issues, especially if the github repository was promoted to be the official repository (not just a mirror).

There are of course somed drawbacks. Github’s issue tracker is extremely limited: it cannot be configured to support sophisticated software development process. Something would need to be done with existing issues: as usual, with yet another migration we would further deteriorate the quality of the database; if we don’t migrate the data then we cannot get rid of the current database for a good while.


(Matt McCormick) #3

GitHub is much easier to use than Jira, vastly more efficient to use than Jira, and it integrates better with the GitHub activity in pull requests for ITK but also other related community projects on GitHub.

While we are not yet ready to promote the GitHub to be the official ITK repository because of other infrastructure issues, we could go ahead and use GitHub Issues as our issue tracker.

I think the clutter caused by a migration of Jira Issues to GitHub would cause more confusion than actual usefulness. Also, I do not think anyone has the cycles to do it properly. @hjmjohnson successfully managed to migrate our Jira instance to a sustainable, free Atlassian cloud-based service for open source projects – the existing issues should be available for reference for the foreseeable future.


(Hans Johnson) #4

+1

Hans


(Pablo Hernandez-Cerdan) #5

I tried, but I couldn’t resist opening the first issue! https://github.com/InsightSoftwareConsortium/ITK/issues/54

This is great, thanks!


(Jon Haitz Legarreta Gorroño) #6

@lassoan I am sorry; I tried to add your email to the JIRA reporters, but for some unknown reason only people having a kitware.com or mail.nih.gov and a couple of other domains that exclude a large part of our community can be added.

We are certainly not managing this correctly, since there was a recent message to the discussion forum from yourself on virtually the same topic. At that time we managed to add Gabriel, and we found no such domain restrictions.

Although switching to GitHub issues, issues reported in JIRA are still important, and to enable a proper follow-up to fix and close the issues, it woud be necessary to address these issues with JIRA.

@hjmjohnson I can’t find where the error lies. I seem to have the rights to add people, but I ignore why the domain rule is there/how to change it.

JON HAITZ


(Hans Johnson) #7

The defaults seems overly restrictive, so I updated them to be more inclusive.

Hans


(Jon Haitz Legarreta Gorroño) #8

@hjmjohnson thanks for doing this. I was able to add @lassoan to the Jira users.

@lassoan if there are issues that you are participating in, you could now try to update them if necessary, and let us know if what has been done allows you to do what you’d expect to.

Thanks.


(Andras Lasso) #9

Thank you, I confirm that my account is functional. I can now add new issue, comment on existing issues, etc.


(Matt McCormick) #10

Thanks @jhlegarreta @hjmjohnson for fixing this :sunny:

Exclusion is certainly not the intention. Migrating to GitHub Issues should help include more of the community, regardless.


(Sean McBride) #11

Could we at least have the github issues start at a number larger than the largest issue number in jira? That would avoid confusion with commit messages in git history that might say something like “fixed issue #123”.


(Matt McCormick) #12

This is a good idea, but it does not appear to be an option in GitHub’s configuration. The previous reference pattern was ITK-NNNN. Now, we should adopt #NN? Thoughts?


(Dženan Zukić) #13

I thought GitHub only supports #NN style for both PRs and issues. So there is no option really than to go with the usual Closes #123 somewhere in commit message.


(Matt McCormick) #14

http://issues.itk.org now points to the GitHub issue tracker :sparkler:


(Matt McCormick) #15

Documentation for the new issue reference syntax is updated here:

http://review.source.kitware.com/#/c/23689/


(Andras Lasso) #16

I’ve reported my first ITK issue via github issue tracker. It was so much easier than finding the issue tracker, look up my username/password, try to remember how to use it (Jira, GitLab, BitBucket, etc. are all slightly different). Probably GitHub’s issue tracker is not a great project management tool, but it makes it very easy to report an error.