[
https://issues.apache.org/jira/browse/LUCENE-10557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17535898#comment-17535898
]
Shad Storhaug commented on LUCENE-10557:
----------------------------------------
The Lucene.NET project switched to GitHub issues 3 years ago, and we were able
to get far more contributor participation than on JIRA, but that may just be
mostly a .NET thing. We held a vote and all participants were unanimous on the
GitHub Issues migration.
It was pretty straightforward for INFRA to do. We made a script to migrate the
open issues to GitHub via API, but there were a couple of issues we had that
you may need to find a workaround for:
# The issues were not added to GitHub in chronological order.
# Since INFRA wouldn't give us permission to the API, we gave the script to
them and the issues were added to GitHub with the INFRA tech as the owner
instead of the original person who submitted the issue.
There is a walkthrough of the process here:
https://gist.github.com/jonmagic/5282384165e0f86ef105#start-an-issue-import%22
We didn't disable JIRA support, but we didn't really have to because we
couldn't get users to participate on it, anyway. But that is something you will
also need to take into consideration.
> Migrate to GitHub issue from Jira?
> ----------------------------------
>
> Key: LUCENE-10557
> URL: https://issues.apache.org/jira/browse/LUCENE-10557
> Project: Lucene - Core
> Issue Type: Sub-task
> Reporter: Tomoko Uchida
> Priority: Major
>
> A few (not the majority) Apache projects already use the GitHub issue instead
> of Jira. For example,
> Airflow: [https://github.com/apache/airflow/issues]
> BookKeeper: [https://github.com/apache/bookkeeper/issues]
> So I think it'd be technically possible that we move to GitHub issue. I have
> little knowledge of how to proceed with it, I'd like to discuss whether we
> should migrate to it, and if so, how to smoothly handle the migration.
> The major tasks would be:
> * Get a consensus about the migration among committers
> * Enable Github issue on the lucene's repository (currently, it is disabled
> on it)
> * Build the convention or rules for issue label/milestone management
> * Choose issues that should be moved to GitHub (I think too old or obsolete
> issues can remain Jira.)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
