If the consensus is to move to git, I think we could see if ASF Infra team can 
move the repo.
If they tell us that it is best for us to handle the move, I can look into it.
Moving the history is easy, the one issue for me is the existing GitHub mirror. 
That would need to be changed to mirror the gitbox.apache.org poi repo (when 
that is created).

Should we have a vote about moving to git first?

On 2025/06/17 04:00:59 stanton fisque wrote:
> TBH svn clients are easy to get.  
> 
> but that's not a good reason to stick with svn.  a move to git would probably 
> revitalize the ci/cd pipeline for this project.   the only real problem i 
> see, is who wants to spend the effort to move the repo history over.
> 
>  
> Stanton Fisque
> principal technologist
> latticeware.com
> portland, oregon
> 
> > On Jun 16, 2025, at 19:36 PM, Axel Howind <a...@dua3.com> wrote:
> > 
> > Definitely move to GitHub and not create another workaround workflow to 
> > keep SVN alive. Tools drop SVN support (I think most already have), and 
> > just getting a working SVN client is not as easy as it should be (probably 
> > depends on platform).
> > 
> >> Am 17.06.2025 um 02:47 schrieb PJ Fanning <fannin...@apache.org>:
> >> 
> >> I would support moving to git.
> >> GitHub CI has started working on our GitHub mirror. For ages, only
> >> commits to the trunk branch triggered jobs but now we are seeing PRs
> >> lead to jobs triggering.
> >> Our main CI jobs are on https://ci-builds.apache.org/ though.
> >> 
> >>> On Mon, 16 Jun 2025 at 20:11, Dave Fisher <w...@apache.org> wrote:
> >>> 
> >>> Hi Devs,
> >>> 
> >>> Over the weekend I saw PJ was triaging some PRs from a contributor, and 
> >>> thought I would take a look at some of the older ones and do some triage. 
> >>> Because of the fact that GitHub.com/apache/poi is git mirror of svn I was 
> >>> unable to close these PRs. I can close these issues from a svn commit 
> >>> message:
> >>> 
> >>> svn ci -m ‘closes #123, closes #345’
> >>> 
> >>> Here’s the GH docs about the commit message: 
> >>> https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword
> >>> 
> >>> If there are no objections I’ll create a file called `.svn-gh-pr-closer`, 
> >>> append notes, and commit messages.
> >>> 
> >>> The alternative would be to migrate over to GitHub. One prospective way 
> >>> to start would be to add CI workflows to GH.
> >>> 
> >>> Best,
> >>> Dave
> >>> ---------------------------------------------------------------------
> >>> 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
> >> 
> > 
> > ---------------------------------------------------------------------
> > 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