[
https://issues.apache.org/jira/browse/LUCENE-10557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17542180#comment-17542180
]
Tomoko Uchida edited comment on LUCENE-10557 at 5/25/22 6:37 PM:
-----------------------------------------------------------------
We are having a long discuss thread on the dev list and many issues are posed.
Here is a short summary (with my brief thoughts/opinions).
* Concerns for political neutrality of GitHub - in other words, concerns for
account bans with no good reason
** Seems there are several cases (including rumors) of GitHub account bans.
It's unclear whether they violate its terms of policy or not, and we won't be
able to correctly assess the risk to me. I would defer the judgment to the
individuals.
** For developers who don't use GitHub for whatever reason, we will always
support contribution paths that do not rely on GitHub. Patches via Jira will be
a decent option for good.
* Concerns for its parent company, Microsoft
** I'd defer the judgment on that to the individuals for the same reason for
the previous subject. One thing I could say is, that the recent trend in their
direction is GOOD - they support/sponsor OSS and Java communities and even
publish very popular open-source software (VSCode and LightGBM are outstanding
examples I think).
* Concerns for lack of issue workflow and simpler metadata management
** From the practical viewpoint, it fully makes sense to me that many people
talked about it. We would need to carefully think of how to control versions
and issue/PR metadata. Large projects that are fully operated on GitHub
overcome this shortcoming in various ways - organized issue templates with
fixed label sets would be an example. I think we will have a sandbox repository
outside ASF, then try some experiments on it before actual migration.
* Security issues that only PMC members are allowed to be accessed
** We will be able to continue to use Jira for this purpose, or we could even
have an issue-only private GitHub repository for Lucene?
* Concerns for migration of whole Jira issue history to GitHub issue
** I don't think it is possible. I'm almost sure there will be some
information losses if we attempt to migrate the whole Jira issue with
metadata/history into Github. Rather than trying to do that, I would prefer to
let Jira issues as is, then simply refer them.
** If we don't aim at perfection, I think we'll be able to migrate all (or
part of) issues with APIs as Shad Storhaug kindly shared in this comment.
Aside from those concerns, there seems no disagreement with GitHub is superior
to Jira in terms of overall UX design, and most new developers like it.
was (Author: tomoko uchida):
We are having a long discuss thread on the dev list and many issues are posed.
Here is a short summary (with my brief thoughts/opinions).
* Concerns for political neutrality of GitHub - in other words, concerns for
account bans with no good reason
** Seems there are several cases (including rumors) of GitHub account bans.
It's unclear whether they violate its terms of policy or not, and we won't be
able to correctly assess the risk to me. I would defer the judgment to the
individuals.
** For developers who don't use GitHub regardless of the reason, we will
always support contribution paths that do not rely on GitHub. Patches via Jira
will be a decent option for good.
* Concerns for its parent company, Microsoft
** I'd defer the judgment on that to the individuals for the same reason for
the previous subject. One thing I could say is, that the recent trend in their
direction is GOOD - they support/sponsor OSS and Java communities and even
publish very popular open-source software (VSCode and LightGBM are outstanding
examples I think).
* Concerns for lack of issue workflow and simpler metadata management
** From the practical viewpoint, it fully makes sense to me that many people
talked about it. We would need to carefully think of how to control versions
and issue/PR metadata. Large projects that are fully operated on GitHub
overcome this shortcoming in various ways - organized issue templates with
fixed label sets would be an example. I think we will have a sandbox repository
outside ASF, then try some experiments on it before actual migration.
* Security issues that only PMC members are allowed to be accessed
** We will be able to continue to use Jira for this purpose, or we could even
have an issue-only private GitHub repository for Lucene?
* Concerns for migration of whole Jira issue history to GitHub issue
** I don't think it is possible. I'm almost sure there will be some
information losses if we attempt to migrate the whole Jira issue with
metadata/history into Github. Rather than trying to do that, I would prefer to
let Jira issues as is, then simply refer them.
** If we don't aim at perfection, I think we'll be able to migrate all (or
part of) issues with APIs as Shad Storhaug kindly shared in [this
comment|https://issues.apache.org/jira/browse/LUCENE-10557?focusedCommentId=17535898&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17535898].
Aside from those concerns, there seems no disagreement with GitHub is superior
to Jira in terms of overall UX design, and most new developers like it.
> 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
