[BUG] Lack of data portability #248

New Issue

Open

opened 2023-01-15 22:51:23 +00:00 by thatonecalculator · 6 comments

thatonecalculator commented

2023-01-15 22:51:23 +00:00

I'm unsure if this is an issue with Forgejo itself or just Codeberg, but regardless this is bad. I can't properly migrate https://codeberg.org/calckey/calckey with issues + PRs due to ratelimiting, and I see no way to do an offline export.

https://stop.voring.me/notes/9a1j0a0x7w

😕 1

tallship commented

2023-01-15 23:10:19 +00:00

Yes this is of some significant measure of import, and deserves a high priority.

earl-warren commented

2023-01-15 23:53:45 +00:00

Owner

Rate limiting is a per-instance issue, you should file an issue https://codeberg.org/Codeberg/Community/issues

👍 1

thatonecalculator referenced this issue from Codeberg/Community

2023-01-16 00:13:22 +00:00

Remove ratelimits for migrating repositories #896

Gusted commented

2023-01-17 00:24:38 +00:00

Owner

@xy Is point on, there's no standardized way to do this. We can give you the raw data(that isn't the difficult part) and leave it at that, but that would be evil IMO.

F3 is an obvious choice to represent the data in. @earl-warren how "stable" is the forgejo-f3 branch? Is it stable enough to hook to be used for a "export repository" button as well the import functionality?

@xy Is point on, there's no standardized way to do this. We can give you the raw data(that isn't the difficult part) and leave it at that, but that would be _evil_ IMO. [F3](https://lab.forgefriends.org/friendlyforgeformat) is an obvious choice to represent the data in. @earl-warren how "stable" is the forgejo-f3 branch? Is it stable enough to hook to be used for a "export repository" button as well the import functionality?

xy commented

2023-01-17 00:54:33 +00:00

Owner

@xy Is point on, there's no standardized way to do this.

Here's what I wrote on fedi about this topic, in case anyone is confused what that's referring to.

The real problem is that there's no standardized way to store issues and PRs using Git. Sure, there are some existing projects like git-bug for this, but none of them are widely adopted and it would be difficult to add support for it in Forgejo.

Instead, for ForgeFed we're creating a JSON vocabulary for storing, importing, and exporting forge data, but this is still a WIP right now.

> @xy Is point on, there's no standardized way to do this. Here's what I [wrote on fedi about this topic](https://social.exozy.me/@a/109695851415405382), in case anyone is confused what that's referring to. > The real problem is that there's no standardized way to store issues and PRs using Git. Sure, there are some existing projects like git-bug for this, but none of them are widely adopted and it would be difficult to add support for it in Forgejo. > > Instead, for ForgeFed we're creating a JSON vocabulary for storing, importing, and exporting forge data, but this is still a WIP right now.

dachary added the

bug

label 2023-01-20 10:24:53 +00:00

earl-warren changed title from ~~Lack of data portability~~ to [BUG] Lack of data portability

2023-02-28 11:22:33 +00:00

Ryuno-Ki commented

2023-03-03 18:04:20 +00:00

FWIW If I would apply for Prototype Fund I would take on this project. Happy to collaborate on it. Deadline for application is end of March 2023.

👍 1

earl-warren added the