You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@poi.apache.org by Vladimir Sitnikov <si...@gmail.com> on 2022/08/18 05:11:35 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 POI users browse code (including POI code) in GitHub,
and they would likely use GitHub PRs (POI 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 Dave Fisher <wa...@comcast.net>.
ASF projects must store source and source releases on ASF controlled properties. A significant amount of work has been done in the last decade to connect Gitbox with GitHub.
If anyone personally has trouble with Microsoft’s owning GitHub they can use the gitbox mirrors.
14 years ago we had significant discussions around trusting Microsoft. Let’s not go there again.
If someone wants to volunteer to make CodeBerg or Gitlab or whatever work with the ASF you are looking at a major effort.
Sent from my iPhone
> On Aug 18, 2022, at 5:41 AM, Yegor Kozlov <ye...@gmail.com> wrote:
>
> GitHub is cool and personally, I much prefer GitHub PRs to Bugzilla.
> There are two questions though:
>
> 1. Github is Apache-friendly, but it is not owned by ASF. For whatever
> reasons they can change their policy, access, etc. and we won't have
> control over it. It's hypothetical, but who knows?
>
> 2. What will happen to the mail list archives with links to Bugzilla ?
> Will it possible to redirect Bugzilla urls to the migrated GitHub Issues?
>
> Regards,
> Yegor
>
>> On Thu, Aug 18, 2022 at 3:21 PM Peter Keller <pk...@globalphasing.com>
>> wrote:
>>
>> Dear all,
>>
>> When considering a move like this, you might like to also consider
>> alternatives to GitHub. I am not going to argue strongly for one service
>> over another, but just note that there is continuing sensitivity for
>> some over Microsoft's policies with respect to GitHub. The Software
>> Freedom Conservancy recently suggested CodeBerg and SourceHut as
>> alternatives: see https://sfconservancy.org/GiveUpGitHub/
>>
>> Regards,
>>
>> Peter.
>>
>>> On 18/08/2022 12:31, PJ Fanning wrote:
>>> Thanks Vladimir for bringing this up. I think it would be a good idea to
>> have a discussion on this list before anyone dedicates too much effort.
>>>
>>> My own opinion is that it would be great to get off bugzilla. I see the
>> merit in using Github instead of Jira - because Github is an integrated
>> environment supporting Issues, Pull Requests and Continuous Integration.
>>>
>>> I would argue that maybe we could consider also moving to Git (away from
>> Subversion). I have a big preference for Pull Requests over patch files
>> being attached to Bugzilla. These patch files get stale very quickly while
>> Git/Github provides good tooling for rebasing or merging the latest
>> trunk/main branch changes into PRs.
>>>
>>> One of the requirements of efforts OSSF Scorecard [1] and SLSA [2] is
>> that code commits are peer reviewed and PRs are a good way to do this. We
>> probably want to get away from having ASF committers committing code
>> directly to svn or git trunk/main branch.
>>>
>>> [1] https://github.com/ossf/scorecard
>>> [2] https://slsa.dev/
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Thursday 18 August 2022 at 10:48:18 IST, Vladimir Sitnikov <
>> sitnikov.vladimir@gmail.com> wrote:
>>>
>>>
>>>
>>>
>>>
>>> Just in case, I can prepare a throwaway repository with migrated
>>> issues/attachments for POI.
>>> I would need an export from Bugzilla database for POI issues.
>>> You could ask it from INFRA like in
>>> https://issues.apache.org/jira/browse/INFRA-23475.
>>>
>>>> Do you have examples of successful transition from Bugzilla to GitHub
>>>> issues for Apache projects?
>>> Well, there are only a few active Apache projects that still use
>> Bugzilla.
>>> Many migrated to JIRA some time ago.
>>>
>>> Apache Lucene migrates from JIRA to GitHub Issues right now:
>>> * https://github.com/apache/lucene/issues/993
>>>
>>> Apache Airflow moved from JIRA to GitHub several years ago:
>>> * https://lists.apache.org/thread/g4sc91y585ypc7tgphlhvxt3v8nqsg5d
>>> * See https://github.com/apache/airflow/releases
>>> * See https://github.com/apache/airflow/issues
>>>
>>> ---
>>>
>>> LLVM project migrated 50'000+ issues from Bugzilla to GitHub in Nov 2021:
>>> * Here's the result: https://github.com/llvm/llvm-project/issues
>>> * https://github.com/llvm/llvm-project/issues/52603
>>> * https://github.com/llvm/llvm-iwg/issues/56
>>>
>>> Coq project migrated 5000 issues from Bugzilla to GitHub:
>>> * https://www.theozimmermann.net/2017/10/bugzilla-to-github/
>>>
>>> Spring project migrated from JIRA to GitHub in 2019:
>>> *
>>>
>> https://spring.io/blog/2019/01/15/spring-framework-s-migration-from-jira-to-github-issues
>>>
>>> Sping Data project migrated from JIRA to GitHub in 2021:
>>> *
>>>
>> https://spring.io/blog/2021/01/07/spring-data-s-migration-from-jira-to-github-issues
>>>
>>>
>>> Vladimir
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
>>> For additional commands, e-mail: dev-help@poi.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
>> For additional commands, e-mail: dev-help@poi.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: Migrate from Bugzilla to GitHub Issues
Posted by Vladimir Sitnikov <si...@gmail.com>.
>2. What will happen to the mail list archives with links to Bugzilla ?
>Will it possible to redirect Bugzilla urls to the migrated GitHub Issues?
I have not explored the possibility to install automatic redirects,
however, for JMeter we'll add a comment to every bug that links the
corresponding GitHub issue.
I know Spring uses a pattern where their JIRA links redirect to GitHub
unless there's "?redirect=false" in the URL.
Vladimir
Re: Migrate from Bugzilla to GitHub Issues
Posted by Yegor Kozlov <ye...@gmail.com>.
GitHub is cool and personally, I much prefer GitHub PRs to Bugzilla.
There are two questions though:
1. Github is Apache-friendly, but it is not owned by ASF. For whatever
reasons they can change their policy, access, etc. and we won't have
control over it. It's hypothetical, but who knows?
2. What will happen to the mail list archives with links to Bugzilla ?
Will it possible to redirect Bugzilla urls to the migrated GitHub Issues?
Regards,
Yegor
On Thu, Aug 18, 2022 at 3:21 PM Peter Keller <pk...@globalphasing.com>
wrote:
> Dear all,
>
> When considering a move like this, you might like to also consider
> alternatives to GitHub. I am not going to argue strongly for one service
> over another, but just note that there is continuing sensitivity for
> some over Microsoft's policies with respect to GitHub. The Software
> Freedom Conservancy recently suggested CodeBerg and SourceHut as
> alternatives: see https://sfconservancy.org/GiveUpGitHub/
>
> Regards,
>
> Peter.
>
> On 18/08/2022 12:31, PJ Fanning wrote:
> > Thanks Vladimir for bringing this up. I think it would be a good idea to
> have a discussion on this list before anyone dedicates too much effort.
> >
> > My own opinion is that it would be great to get off bugzilla. I see the
> merit in using Github instead of Jira - because Github is an integrated
> environment supporting Issues, Pull Requests and Continuous Integration.
> >
> > I would argue that maybe we could consider also moving to Git (away from
> Subversion). I have a big preference for Pull Requests over patch files
> being attached to Bugzilla. These patch files get stale very quickly while
> Git/Github provides good tooling for rebasing or merging the latest
> trunk/main branch changes into PRs.
> >
> > One of the requirements of efforts OSSF Scorecard [1] and SLSA [2] is
> that code commits are peer reviewed and PRs are a good way to do this. We
> probably want to get away from having ASF committers committing code
> directly to svn or git trunk/main branch.
> >
> > [1] https://github.com/ossf/scorecard
> > [2] https://slsa.dev/
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > On Thursday 18 August 2022 at 10:48:18 IST, Vladimir Sitnikov <
> sitnikov.vladimir@gmail.com> wrote:
> >
> >
> >
> >
> >
> > Just in case, I can prepare a throwaway repository with migrated
> > issues/attachments for POI.
> > I would need an export from Bugzilla database for POI issues.
> > You could ask it from INFRA like in
> > https://issues.apache.org/jira/browse/INFRA-23475.
> >
> >> Do you have examples of successful transition from Bugzilla to GitHub
> >> issues for Apache projects?
> > Well, there are only a few active Apache projects that still use
> Bugzilla.
> > Many migrated to JIRA some time ago.
> >
> > Apache Lucene migrates from JIRA to GitHub Issues right now:
> > * https://github.com/apache/lucene/issues/993
> >
> > Apache Airflow moved from JIRA to GitHub several years ago:
> > * https://lists.apache.org/thread/g4sc91y585ypc7tgphlhvxt3v8nqsg5d
> > * See https://github.com/apache/airflow/releases
> > * See https://github.com/apache/airflow/issues
> >
> > ---
> >
> > LLVM project migrated 50'000+ issues from Bugzilla to GitHub in Nov 2021:
> > * Here's the result: https://github.com/llvm/llvm-project/issues
> > * https://github.com/llvm/llvm-project/issues/52603
> > * https://github.com/llvm/llvm-iwg/issues/56
> >
> > Coq project migrated 5000 issues from Bugzilla to GitHub:
> > * https://www.theozimmermann.net/2017/10/bugzilla-to-github/
> >
> > Spring project migrated from JIRA to GitHub in 2019:
> > *
> >
> https://spring.io/blog/2019/01/15/spring-framework-s-migration-from-jira-to-github-issues
> >
> > Sping Data project migrated from JIRA to GitHub in 2021:
> > *
> >
> https://spring.io/blog/2021/01/07/spring-data-s-migration-from-jira-to-github-issues
> >
> >
> > Vladimir
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
> > For additional commands, e-mail: dev-help@poi.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
> For additional commands, e-mail: dev-help@poi.apache.org
>
>
Re: Migrate from Bugzilla to GitHub Issues
Posted by Peter Keller <pk...@globalphasing.com>.
Dear all,
When considering a move like this, you might like to also consider
alternatives to GitHub. I am not going to argue strongly for one service
over another, but just note that there is continuing sensitivity for
some over Microsoft's policies with respect to GitHub. The Software
Freedom Conservancy recently suggested CodeBerg and SourceHut as
alternatives: see https://sfconservancy.org/GiveUpGitHub/
Regards,
Peter.
On 18/08/2022 12:31, PJ Fanning wrote:
> Thanks Vladimir for bringing this up. I think it would be a good idea to have a discussion on this list before anyone dedicates too much effort.
>
> My own opinion is that it would be great to get off bugzilla. I see the merit in using Github instead of Jira - because Github is an integrated environment supporting Issues, Pull Requests and Continuous Integration.
>
> I would argue that maybe we could consider also moving to Git (away from Subversion). I have a big preference for Pull Requests over patch files being attached to Bugzilla. These patch files get stale very quickly while Git/Github provides good tooling for rebasing or merging the latest trunk/main branch changes into PRs.
>
> One of the requirements of efforts OSSF Scorecard [1] and SLSA [2] is that code commits are peer reviewed and PRs are a good way to do this. We probably want to get away from having ASF committers committing code directly to svn or git trunk/main branch.
>
> [1] https://github.com/ossf/scorecard
> [2] https://slsa.dev/
>
>
>
>
>
>
>
>
>
> On Thursday 18 August 2022 at 10:48:18 IST, Vladimir Sitnikov <si...@gmail.com> wrote:
>
>
>
>
>
> Just in case, I can prepare a throwaway repository with migrated
> issues/attachments for POI.
> I would need an export from Bugzilla database for POI issues.
> You could ask it from INFRA like in
> https://issues.apache.org/jira/browse/INFRA-23475.
>
>> Do you have examples of successful transition from Bugzilla to GitHub
>> issues for Apache projects?
> Well, there are only a few active Apache projects that still use Bugzilla.
> Many migrated to JIRA some time ago.
>
> Apache Lucene migrates from JIRA to GitHub Issues right now:
> * https://github.com/apache/lucene/issues/993
>
> Apache Airflow moved from JIRA to GitHub several years ago:
> * https://lists.apache.org/thread/g4sc91y585ypc7tgphlhvxt3v8nqsg5d
> * See https://github.com/apache/airflow/releases
> * See https://github.com/apache/airflow/issues
>
> ---
>
> LLVM project migrated 50'000+ issues from Bugzilla to GitHub in Nov 2021:
> * Here's the result: https://github.com/llvm/llvm-project/issues
> * https://github.com/llvm/llvm-project/issues/52603
> * https://github.com/llvm/llvm-iwg/issues/56
>
> Coq project migrated 5000 issues from Bugzilla to GitHub:
> * https://www.theozimmermann.net/2017/10/bugzilla-to-github/
>
> Spring project migrated from JIRA to GitHub in 2019:
> *
> https://spring.io/blog/2019/01/15/spring-framework-s-migration-from-jira-to-github-issues
>
> Sping Data project migrated from JIRA to GitHub in 2021:
> *
> https://spring.io/blog/2021/01/07/spring-data-s-migration-from-jira-to-github-issues
>
>
> Vladimir
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
> For additional commands, e-mail: dev-help@poi.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: Migrate from Bugzilla to GitHub Issues
Posted by PJ Fanning <fa...@yahoo.com.INVALID>.
Thanks Vladimir for bringing this up. I think it would be a good idea to have a discussion on this list before anyone dedicates too much effort.
My own opinion is that it would be great to get off bugzilla. I see the merit in using Github instead of Jira - because Github is an integrated environment supporting Issues, Pull Requests and Continuous Integration.
I would argue that maybe we could consider also moving to Git (away from Subversion). I have a big preference for Pull Requests over patch files being attached to Bugzilla. These patch files get stale very quickly while Git/Github provides good tooling for rebasing or merging the latest trunk/main branch changes into PRs.
One of the requirements of efforts OSSF Scorecard [1] and SLSA [2] is that code commits are peer reviewed and PRs are a good way to do this. We probably want to get away from having ASF committers committing code directly to svn or git trunk/main branch.
[1] https://github.com/ossf/scorecard
[2] https://slsa.dev/
On Thursday 18 August 2022 at 10:48:18 IST, Vladimir Sitnikov <si...@gmail.com> wrote:
Just in case, I can prepare a throwaway repository with migrated
issues/attachments for POI.
I would need an export from Bugzilla database for POI issues.
You could ask it from INFRA like in
https://issues.apache.org/jira/browse/INFRA-23475.
>Do you have examples of successful transition from Bugzilla to GitHub
>issues for Apache projects?
Well, there are only a few active Apache projects that still use Bugzilla.
Many migrated to JIRA some time ago.
Apache Lucene migrates from JIRA to GitHub Issues right now:
* https://github.com/apache/lucene/issues/993
Apache Airflow moved from JIRA to GitHub several years ago:
* https://lists.apache.org/thread/g4sc91y585ypc7tgphlhvxt3v8nqsg5d
* See https://github.com/apache/airflow/releases
* See https://github.com/apache/airflow/issues
---
LLVM project migrated 50'000+ issues from Bugzilla to GitHub in Nov 2021:
* Here's the result: https://github.com/llvm/llvm-project/issues
* https://github.com/llvm/llvm-project/issues/52603
* https://github.com/llvm/llvm-iwg/issues/56
Coq project migrated 5000 issues from Bugzilla to GitHub:
* https://www.theozimmermann.net/2017/10/bugzilla-to-github/
Spring project migrated from JIRA to GitHub in 2019:
*
https://spring.io/blog/2019/01/15/spring-framework-s-migration-from-jira-to-github-issues
Sping Data project migrated from JIRA to GitHub in 2021:
*
https://spring.io/blog/2021/01/07/spring-data-s-migration-from-jira-to-github-issues
Vladimir
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: Migrate from Bugzilla to GitHub Issues
Posted by Vladimir Sitnikov <si...@gmail.com>.
Just in case, I can prepare a throwaway repository with migrated
issues/attachments for POI.
I would need an export from Bugzilla database for POI issues.
You could ask it from INFRA like in
https://issues.apache.org/jira/browse/INFRA-23475.
>Do you have examples of successful transition from Bugzilla to GitHub
>issues for Apache projects?
Well, there are only a few active Apache projects that still use Bugzilla.
Many migrated to JIRA some time ago.
Apache Lucene migrates from JIRA to GitHub Issues right now:
* https://github.com/apache/lucene/issues/993
Apache Airflow moved from JIRA to GitHub several years ago:
* https://lists.apache.org/thread/g4sc91y585ypc7tgphlhvxt3v8nqsg5d
* See https://github.com/apache/airflow/releases
* See https://github.com/apache/airflow/issues
---
LLVM project migrated 50'000+ issues from Bugzilla to GitHub in Nov 2021:
* Here's the result: https://github.com/llvm/llvm-project/issues
* https://github.com/llvm/llvm-project/issues/52603
* https://github.com/llvm/llvm-iwg/issues/56
Coq project migrated 5000 issues from Bugzilla to GitHub:
* https://www.theozimmermann.net/2017/10/bugzilla-to-github/
Spring project migrated from JIRA to GitHub in 2019:
*
https://spring.io/blog/2019/01/15/spring-framework-s-migration-from-jira-to-github-issues
Sping Data project migrated from JIRA to GitHub in 2021:
*
https://spring.io/blog/2021/01/07/spring-data-s-migration-from-jira-to-github-issues
Vladimir
Re: Migrate from Bugzilla to GitHub Issues
Posted by Sergey Vladimirov <vl...@gmail.com>.
Hi, Vladimir,
Do you have examples of successful transition from Bugzilla to GitHub
issues for Apache projects? (already completed ones)
Best regards,
Sergey
Чт, 18 авг. 2022 г. в 08:11, Vladimir Sitnikov <sitnikov.vladimir@gmail.com
>:
> 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 POI users browse code (including POI code) in GitHub,
> and they would likely use GitHub PRs (POI 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
>
--
Sergey Vladimirov