You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Vladimir Sitnikov <si...@gmail.com> on 2022/08/18 04:57:23 UTC
Migrate from Bugzilla to GitHub Issues
Hi,
Have you considered migrating from Bugzilla to GitHub Issues?
I think co-locating issues, code, and PRs at GitHub would make it easier to
browse both issues and code.
I guess many Tomcat users browse code (including Tomcat code) in GitHub,
and they would likely use GitHub PRs (Tomcat PRs and PRs for the other
projects).
It is inconvenient to require Bugzilla login for the sole purpose of filing
an issue.
It is inconvenient that search over bugs is disconnected from search over
code.
If bugs are migrated to GitHub, then a single GitHub search would work for
everything: code, issues, PRs
GitHub allows richer comment formatting (e.g. code highlight).
GitHub shows code preview when you mention link to code in an issue comment.
Moving issues to GitHub would unlock cross-references between projects
(e.g. users could mention Tomcat issues)
so others can see which projects reference the same issue, and sometimes
you could peek into the workarounds.
I'm working on migrating Apache JMeter (Bugzilla -> GitHub Issues), see
https://lists.apache.org/thread/xmccss17s6sm8wzcm56d7sr6py663s7w ,
and I have a migration script https://github.com/vlsi/bugzilla2github
It preserves bugs, comments, attachments, and links between bugs.
Here's a recent dry-run for JMeter:
https://github.com/vlsi/tmp-jmeter-issues
For reference, the first bug in JMeter was filed on 2003, and we look
forward to migrating all the ~5K bugs to GitHub issues.
LLVM moved from Bugzilla to GitHub a year ago (50K bugs since 2003)
WDYT?
Vladimir
Re: Migrate from Bugzilla to GitHub Issues
Posted by Vladimir Sitnikov <si...@gmail.com>.
>GitLab is certainly there and is well-known,
>and anyone can create their own. It is not that hard.
For reference, it would be hard to integrate Gitlab with ASF infra.
>The result is that they are scattered all over my GMail Inbox
Great. Thank you for the suggestion.
I knew something was wrong with GitBox notifications, however, I was not
sure what was wrong,
so I just deleted GitBox emails and used GitHub notifications instead.
I've bumped the relevant 3y.o. thread:
https://lists.apache.org/thread/1h94t08dtfr3wc86x46ogv7dbb1y64y7
Hopefully, it won't take long to remove the username, and action from the
email subject.
Vladimir
Re: Migrate from Bugzilla to GitHub Issues
Posted by Konstantin Kolinko <kn...@gmail.com>.
чт, 18 авг. 2022 г. в 15:13, Vladimir Sitnikov <si...@gmail.com>:
>
> > 1. It is better to stay with a solution owned by ASF as much as possible.
> > For political reasons such as independence.
>
> AFAIK, the ASF is incorporated in the USA, so the organization must
> follow the USA laws.
> Are you sure the ASF provides "political independence"?
I mean that the mission of ASF is to be a vendor-neutral place where people
(employed by different companies)
can collaborate to develop free software for the public good.
The mission of Microsoft (the current owner of GitHub) is that of a
commercial entity,
and is different from ours.
What Microsoft does is governed by laws of the State of Washington, US,
maybe by laws of Ireland (where is their unit that provides marketing
and sales for the EMEA region),
and generally by their business interests.
Legally, it is expressed in their written agreements,
or in public agreements such as Terms of Service, EULA etc.
Sometimes corporations do what they feel is in their business interests,
regardless of whether there are actual laws.
ASF is governed by the laws of the State of Delaware, US,
and has a different mission, public image, etc.
> > GitHub is not the only git hosting service out there.
>
> To my best knowledge, the ASF supports only two git hosting services:
> a) GitBox (see https://git.apache.org/)
> b) GitHub (it any case it is mirrored to GitBox)
As with ASF mailing lists, that have a number of independent archives,
there can be (now or in the future) any number of git mirrors.
GitBox at ASF is the main repository.
GitHub is a mirror.
I would be happy to accept a PR from any other git hosting service.
> To my best knowledge, GitHub is the only git service that integrates
> issue tracking and code hosting.
GitLab is certainly there and is well-known,
and anyone can create their own. It is not that hard.
https://docs.gitlab.com/ee/user/project/issues/
>
> Just in case, GitHub uses markdown for the format, so the emails in
> text form are readable.
GitHub (or maybe GitBox) sends e-mails that are titled like
"[GitHub] [tomcat-jakartaee-migration] aooohan commented on issue #29: ..."
The result is that they are scattered all over my GMail Inbox,
are split by a user name (aooohan in this case) and action (commented,
created, closed).
It is hard to see the whole discussion without going to the GitHub site.
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Migrate from Bugzilla to GitHub Issues
Posted by Vladimir Sitnikov <si...@gmail.com>.
> 1. It is better to stay with a solution owned by ASF as much as possible.
> For political reasons such as independence.
AFAIK, the ASF is incorporated in the USA, so the organization must
follow the USA laws.
Are you sure the ASF provides "political independence"?
> GitHub is not the only git hosting service out there.
To my best knowledge, the ASF supports only two git hosting services:
a) GitBox (see https://git.apache.org/)
b) GitHub (it any case it is mirrored to GitBox)
GitBox does not support issue tracking, so would you please clarify
what do you mean by
"is not the only git hosting service out there"?
To my best knowledge, GitHub is the only git service that integrates
issue tracking and code hosting.
At the same time, Tomcat hosts code at GitHub, and there's a
significant number of PR contributions via GitHub:
https://github.com/apache/tomcat/pulls, so it looks reasonable to move
issues closer to PRs and code.
> 2. E-mails allowed to the mailing lists have to be plain text.
Well, GitBox does produce text emails that look not much different
from Bugzilla emails to me.
Just in case, GitHub uses markdown for the format, so the emails in
text form are readable.
Here's a recent bug where comment already uses markdown, so the same
thing would look better in GitHub UI:
https://bz.apache.org/bugzilla/show_bug.cgi?id=66191
"issue created" mail:
https://lists.apache.org/thread/4q6vmr0qq7w3pomtx1qpyj2gy8f0576h
"issue commented" mail:
https://lists.apache.org/thread/rch13owttglnpq2gfg6xhz00kw73on71
Would you please check the above notifications and clarify why you
think Bugzilla emails are better?
Vladimir
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Migrate from Bugzilla to GitHub Issues
Posted by Emmanuel Bourg <eb...@apache.org>.
On 18/08/2022 10:51, Konstantin Kolinko wrote:
>>
>> Have you considered migrating from Bugzilla to GitHub Issues?
>>
>
> I am -1.
>
> 1. It is better to stay with a solution owned by ASF as much as possible.
Same feeling here, I like how GitHub ties the code hosting and the issue
tracker, but I think it's important the ASF keeps the control of its
tools. If ever the ASF replaces GitBox with GitLab or Gitea I'd support
moving the issue tracker.
Emmanuel Bourg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Migrate from Bugzilla to GitHub Issues
Posted by Han Li <ao...@gmail.com>.
> 2022年8月18日 16:51，Konstantin Kolinko <kn...@gmail.com> 写道：
>
> чт, 18 авг. 2022 г. в 07:57, Vladimir Sitnikov <si...@gmail.com>:
>>
>> Hi,
>>
>>
>> Have you considered migrating from Bugzilla to GitHub Issues?
>>
>
> I am -1.
>
> 1. It is better to stay with a solution owned by ASF as much as possible.
+1
Han
>
> For political reasons such as independence.
> As well as for redundancy etc.
>
> GitHub is not the only git hosting service out there.
>
>
> Also, recently there were rumors about some developers being banned from GitHub.
> I cannot verify whether those rumors were accurate,
> but overall it looked like something that may happen.
>
>
>> GitHub allows richer comment formatting (e.g. code highlight).
>
> 2. E-mails allowed to the mailing lists have to be plain text.
>
> E-mails from Bugzilla are easier to follow.
>
> Best regards,
> Konstantin Kolinko
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Migrate from Bugzilla to GitHub Issues
Posted by Konstantin Kolinko <kn...@gmail.com>.
чт, 18 авг. 2022 г. в 07:57, Vladimir Sitnikov <si...@gmail.com>:
>
> Hi,
>
>
> Have you considered migrating from Bugzilla to GitHub Issues?
>
I am -1.
1. It is better to stay with a solution owned by ASF as much as possible.
For political reasons such as independence.
As well as for redundancy etc.
GitHub is not the only git hosting service out there.
Also, recently there were rumors about some developers being banned from GitHub.
I cannot verify whether those rumors were accurate,
but overall it looked like something that may happen.
> GitHub allows richer comment formatting (e.g. code highlight).
2. E-mails allowed to the mailing lists have to be plain text.
E-mails from Bugzilla are easier to follow.
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Migrate from Bugzilla to GitHub Issues
Posted by Christopher Schultz <ch...@christopherschultz.net>.
All,
On 8/18/22 08:30, Mark Thomas wrote:
>
>
> On 18/08/2022 13:21, Graham Leggett wrote:
>> On 18 Aug 2022, at 06:57, Vladimir Sitnikov
>> <si...@gmail.com> wrote:
>>
>>> Have you considered migrating from Bugzilla to GitHub Issues?
>>>
>>> I think co-locating issues, code, and PRs at GitHub would make it
>>> easier to
>>> browse both issues and code.
>>
>> -1.
>>
>> GitHub as a service is hosted by someone else, who are in no way
>> obligated to keep the service running for our benefit. Hosted services
>> come and go regularly, and it is an enormous waste of time and effort
>> for people to perform avoidable migrations each time this happens.
>>
>> We mirror to Github because Github did the work to make that happen.
>> It’s great that they did that, but support could be withdrawn at any
>> time and without warning.
>
> The ASF wrote the GitBox <-> GitHub synchronization code as there wasn't
> anything available that would allow us to keep an independent ASF repo
> in sync with a GitHub repo and allow commits to either. It was that sync
> code that opened up the possibility of commits to AS projects via GitHub.
>
> There is also the problem that hosting issue tracking at GitHub requires
> users to sign up for a GitHub account and agree to GitHub's Ts&Cs in
> order to report an issue. There are a small number of users that are not
> prepared to do that.
>
> There are benefits and risks associated with switching to issue tracking
> at GitHub. We need to weigh the one against the other.
>
> As an experiment, we are tracking Migration Tool issues on GitHub. It is
> a small tool so there are only a few issues and limited data. I haven't
> seen anything yet that convinces me that there is a strong argument for
> or against using GitHub issues. If the Tomcat Maven plugin project
> starts to show signs of life, we could try migrating its issues to
> GitHub as a larger experiment.
I am also -1 on migrating from Bugzilla -> GitHub precisely for all the
reasons already mentioned.
While you can't create a GH issue, you can always create a PR that
includes an explanation of the bug. It's not a format Issue, but it does
get the job done.
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Migrate from Bugzilla to GitHub Issues
Posted by Mark Thomas <ma...@apache.org>.
On 18/08/2022 13:21, Graham Leggett wrote:
> On 18 Aug 2022, at 06:57, Vladimir Sitnikov <si...@gmail.com> wrote:
>
>> Have you considered migrating from Bugzilla to GitHub Issues?
>>
>> I think co-locating issues, code, and PRs at GitHub would make it easier to
>> browse both issues and code.
>
> -1.
>
> GitHub as a service is hosted by someone else, who are in no way obligated to keep the service running for our benefit. Hosted services come and go regularly, and it is an enormous waste of time and effort for people to perform avoidable migrations each time this happens.
>
> We mirror to Github because Github did the work to make that happen. It’s great that they did that, but support could be withdrawn at any time and without warning.
The ASF wrote the GitBox <-> GitHub synchronization code as there wasn't
anything available that would allow us to keep an independent ASF repo
in sync with a GitHub repo and allow commits to either. It was that sync
code that opened up the possibility of commits to AS projects via GitHub.
There is also the problem that hosting issue tracking at GitHub requires
users to sign up for a GitHub account and agree to GitHub's Ts&Cs in
order to report an issue. There are a small number of users that are not
prepared to do that.
There are benefits and risks associated with switching to issue tracking
at GitHub. We need to weigh the one against the other.
As an experiment, we are tracking Migration Tool issues on GitHub. It is
a small tool so there are only a few issues and limited data. I haven't
seen anything yet that convinces me that there is a strong argument for
or against using GitHub issues. If the Tomcat Maven plugin project
starts to show signs of life, we could try migrating its issues to
GitHub as a larger experiment.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Migrate from Bugzilla to GitHub Issues
Posted by Graham Leggett <mi...@sharp.fm.INVALID>.
On 18 Aug 2022, at 06:57, Vladimir Sitnikov <si...@gmail.com> wrote:
> Have you considered migrating from Bugzilla to GitHub Issues?
>
> I think co-locating issues, code, and PRs at GitHub would make it easier to
> browse both issues and code.
-1.
GitHub as a service is hosted by someone else, who are in no way obligated to keep the service running for our benefit. Hosted services come and go regularly, and it is an enormous waste of time and effort for people to perform avoidable migrations each time this happens.
We mirror to Github because Github did the work to make that happen. It’s great that they did that, but support could be withdrawn at any time and without warning.
Regards,
Graham
—
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org