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.vladi...@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-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

Reply via email to