[x] +1 - Activate the issue trackers in the GitHub repos and start using them, 
stop opening issues in Jira

Peter

Am 22.06.2022 um 09:38 schrieb Richard Eckart de Castilho:
Hi again,

to bring this up again - I have not heard back from anybody, so I assume there 
is a general
indifference as to which issue tracker UIMA is using - or at least no objection 
to stop
using Jira and instead start using GitHub.

The switch would be a slow one:

- open no new issues on Jira
- close issues on Jira as we go a long working on them
- potentially "move" some issues from Jira to GitHub by opening the issue on 
GitHub and the closing on Jira
- the Jira tracker should remain accessible for historic purposes for the 
foreseeable future

There is still some code that is only in SVN - the migration process for issues 
related to that code would only
commence once it has been moved to a respective GitHub repo.

So to formalize this, I would like to call for a vote on the topic:

[ ] +1 - Activate the issue trackers in the GitHub repos and start using them, 
stop opening issues in Jira
[ ] 0  - I don't care
[ ] -1 - Leave issue trackers in GitHub disabled and keep using Jira

Vote should be cast by Monday June 27th midnight CEST to be counted. Please be 
sure to participate.

-- Richard

On 28. Apr 2022, at 11:19, Richard Eckart de Castilho <r...@apache.org> wrote:

Hi folks,

does anybody have an opinion on giving up Jira in favor of GitHub issues?

I am personally more used to a purely GitHub-based workflow and find

Ups of GitHub:
- the issue management features of GitHub conveniently lightweight and flexible
- the UI reasonably fast

Downs of Jira:
- there are tons of issue types we do not use
- the UI is sluggish
- instead of markdown, a Jira-specific markup language needs to be used
- people cannot access e.g. the changelist report without logging in to Jira

Main differences:
- Jira issues can target multiple versions, GitHub issues can target only a 
single milestone
- In Jira we have one "project", in GitHub, we have one tracker per repo - "cross 
repo" issues would be a thing of the past (maybe a good thing)

Any further input or opinions?

Cheers,

-- Richard

--
Dr. Peter Klügl
Head of Text Mining/Machine Learning

Averbis GmbH
Salzstr. 15
79098 Freiburg
Germany

Fon: +49 761 708 394 0
Fax: +49 761 708 394 10
Email: peter.klu...@averbis.com
Web: https://averbis.com

Headquarters: Freiburg im Breisgau
Register Court: Amtsgericht Freiburg im Breisgau, HRB 701080
Managing Directors: Dr. med. Philipp Daumke, Dr. Kornél Markó

Reply via email to