[
https://issues.apache.org/jira/browse/LUCENE-10557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17531683#comment-17531683
]
Tomoko Uchida commented on LUCENE-10557:
----------------------------------------
Among the tasks I mentioned in the issue description, the most important (and
most difficult?) one could be "Get a consensus about the migration".
I look for explicit feedback (+1 or -1) on this topic from developers.
I'd definitely cast +1; not because I don't like Jira (it works well for me so
far), but because the most development is already going on GitHub.
Consolidation of conversation would be good for improving experiences I think.
> 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
--
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
