Move from github?

[yaxu]

Some have deleted their github accounts for ethical reasons and so are excluded from discussions here.

Gitea looks like it's well maintained and with a familiar interface. I can't see any big disadvantages to moving to that?

[telephon]

Looks interesting! Is it based on Gitlab?

[yaxu]

No I think its a separate code base, and lighter on resources. Migration of issues etc looks straightforward

[ndr-brt]

Ok for me. we shoud learn and adopt another continuous environment system. Don't know what integrates well with gitea

[yaxu]

It looks like there are a couple of options: https://gitea.com/gitea/awesome-gitea#devops

[ndr-brt]

Nice. In the past I used jenkins a lot, and I also explored concourse. Seems like agola, drone and woodpecker have a built-in support for gitea.

[yaxu]

I've put a mirror up on codeberg, which runs gitea: https://codeberg.org/TidalCycles

It seems nice!

If we decide to move there, there's a migration function to bring issues etc across.

edit I removed the mirror, I thought it would be confusing to have both active. If/when we move, we would have needed to delete that anyway and use the migration tool.

[yaxu]

I've tried migrating the vortex project there: https://codeberg.org/TidalCycles/vortex

It only had one issue but seems smooth..

[yaxu]

We moved vortex back to github, as codeberg didn't seem quite there in terms of running ci etc.

But perhaps we could try gitlab? At the same time, we could change the organisational structure a bit to reflect the appearance of strudel and vortex. I propose we have a top-level group 'algopattern' with 'tidalcycles', 'strudel' and 'vortex' as subgroups of that.

There is an import process, but before running it we'd want to have as many people with gitlab accounts as we can so that issues and pull/merge requests are properly assigned.

[yaxu]

I imported feedforward there as a test https://gitlab.com/algopattern/tidalcycles/feedforward