Can I start moving the other projects to GitLab?

[Mihai Nita]

Okapi is released, moved to GitLab, CI working, branches renamed ("main" and "release").

I didn't see any complaints :-)

So can we assume it is all good, and we are not going back?

Because I can start moving all the other projects to GitLab:

• OmegaT Plugin   Last update: 2024-10-06
• Longhorn    Last update: 2024-10-01
• longhorn-js-client    Last update: 2024-06-26
• Okapi Linguistic Tools    Last update: 2024-06-25
• Sandbox    Last update: 2024-02-08
• XLIFF Toolkit    Last update: 2024-01-03
• SRX Repository    Last update: 2023-12-20
• Olifant    Last update: 2022-01-17
• Quest    Last update: 2016-06-07
• Acorn    Last update: 2015-12-09
• Beagle    Last update: 2015-04-23

And I also want to rename branches, to be consistent with Okapi proper.

So we don't have to deal with a mixture of dev / main / master / release / whatever.

The main question is Longhorn, which was usually released at the same time with the Okapi release (a few days off).

If we still want to release it then it would be best to do it before the disruption of the migration and branch renaming.

WDYT?

Thank you,

Mihai

[Chase Tingley]

I have no objection to you migrating the other projects, and I would love it if you could do Longhorn as well -- I had thought maybe you were leaving it for me :)

I will do a 1.47.0 Longhorn release in the next few days to unblock the migration.

--
You received this message because you are subscribed to the Google Groups "okapi-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to okapi-devel...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/okapi-devel/CAK69zbnxX_TEYdOPz6hU2rxDvAAt0BRmS_E2R9gRvW8D1P9_wQ%40mail.gmail.com.

[yves.s...@gmail.com]

+1

--

[Jim Hargrave]

Do all of these projects need to be migrated?

These could remain in bitbucket:

• XLIFF Toolkit

• Quest    Last update: 2016-06-07
• Acorn    Last update: 2015-12-09
• Beagle

• Olifant
• SRX Repository

To view this discussion on the web visit https://groups.google.com/d/msgid/okapi-devel/001401db2032%244b040590%24e10c10b0%24%40gmail.com.

[yves.s...@gmail.com]

Right, there is no need to move Quest, Acorn and Beagle for sure.

Olifant: that the “new” one, that we never completed and has not been updated in many years, so probably no need to move it either.

As for SRX Repository and XLIFF Toolkit, I don’t know: they’re not updated anymore so they can likely stay there.

-ys

[Mihai Nita]

I already copied everything a few days (nights :-) ago.

I know some of the projects have been dormant for a long time.

But I thought it is nicer to have everything in one place.

I've also updated all links to Bitbucket that I was able to find in Okapi.

Thank you Chase for releasing Longhorn, I'm working on it right now.

---

One question I have is what should I try to get building again in CI?

The Okapi README.md has a "Build status" section with badges for 

• Okapi
• XLIFF Toolkit
• Longhorn
• Longhorn JS Client
• OmegaT Plugin
• Olifant

So these are projects that we used to build.

But then I noticed that Olifant uses Okapi 1.41.0.

So there is not much reason for a nightly build, because nothing changes.

Jim said that "These could remain in bitbucket":

• XLIFF Toolkit
• Quest    Last update: 2016-06-07
• Acorn    Last update: 2015-12-09
• Beagle
• Olifant
• SRX Repository

So if I do "what we used to build nightly" minus "what can remain in Bitbucket" I am left with these to get up and running again in CI:

• Okapi
• Longhorn
  
• Longhorn JS Client
• OmegaT Plugin

Mihai

To view this discussion on the web visit https://groups.google.com/d/msgid/okapi-devel/000001db2133%2440a5fbb0%24c1f1f310%24%40gmail.com.

[Chase Tingley]

I got Olifant compiling again a few years ago, but updating the Lucene dependency is a real chore. The old version is still actively used by some people, so it would be nice to support, but I don’t think anyone really has the time. I am glad to keep things in one place, though, so thank you for migrating them all.

To view this discussion on the web visit https://groups.google.com/d/msgid/okapi-devel/CAK69zb%3D5mTdiSTBHJv8-g%2BXoxmjtSp%2BuhenpW4cASSvL0qfXxg%40mail.gmail.com.

[yves.s...@gmail.com]

Thank you both.

To view this discussion on the web visit https://groups.google.com/d/msgid/okapi-devel/CAGRYq4gozDXGPm6Q9msNeVHXRuKhBxdh13gC%3DE5v1qAa%3D%3DF1%3DQ%40mail.gmail.com.

[Mihai Nita]

I also migrated Longhorn and updated the branching model to `main` / `release`

Updated Longhorn, Longhorn JS Client, OmegaT Plugin to run CI on PR / submit / nightly.

And updated the Okapi README.md to show badges for them.

I'm thinking that we should find a way to visibly mark the bitbucket repos as migrated to GitLab.

Removing them completely feels a bit too drastic :-)

And maybe a way to mark the rest of the repos as unmaintained...

Regards,

Mihai

To view this discussion on the web visit https://groups.google.com/d/msgid/okapi-devel/000c01db226f%24327404a0%24975c0de0%24%40gmail.com.