Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Blender moves from Phabricator to Gitea

code.blender.org

Post reply on HN
Print view View original

31–40 of 58 posts

Re: Blender moves from Phabricator to Gitea

#31

Post by jolheiser »

vfclists wrote: post #29
techknowlogick wrote: post #23

Earlier quoted context omitted.

Hi, I'm one of the members of the technical oversight committee of the Gitea project, and am employed to work on Gitea. The reason why the project itself is still on GitHub is due to the massive amount of metadata (20K+ issues and PRs, and all the comments, reactions, and other metadata attached to them) around the project, and the ratelimiting that is slowing the export. All the non-primary repos have long since mov…

I start getting worried about projects when people say stuff like "I'm one of the members of the technical oversight committee of the Gitea project" How many committees are there and how many people on each committee?

The TOC is our owners team, but three are from the company and three are from the community.

The reason to say it as a disclaimer is because we are going to have some bias.

Re: Blender moves from Phabricator to Gitea

#32

Post by bastardoperator »

techknowlogick wrote: post #23
cowmix wrote: post #2

I wonder how Gitea will hold up to all the traffic? Even Gitea hosts their stuff on Github.

Hi, I'm one of the members of the technical oversight committee of the Gitea project, and am employed to work on Gitea. The reason why the project itself is still on GitHub is due to the massive amount of metadata (20K+ issues and PRs, and all the comments, reactions, and other metadata attached to them) around the project, and the ratelimiting that is slowing the export. All the non-primary repos have long since mov…

You can use the API to export all of the metadata in a single request:

https://docs.github.com/en/rest/migrations/orgs#start-an-org...

https://docs.github.com/en/rest/migrations/orgs#download-an-...

Using a Github App you get 15K requests per hour. Even with pagination(100 records per request) you should be able to get at all of this data within a couple of hours. I suspect you lack reliable transformation tools to take github metadata and convert it to gitea versus the limitations of GitHub.

Re: Blender moves from Phabricator to Gitea

#34

Post by techknowlogick »

bastardoperator wrote: post #32
techknowlogick wrote: post #23

Earlier quoted context omitted.

Hi, I'm one of the members of the technical oversight committee of the Gitea project, and am employed to work on Gitea. The reason why the project itself is still on GitHub is due to the massive amount of metadata (20K+ issues and PRs, and all the comments, reactions, and other metadata attached to them) around the project, and the ratelimiting that is slowing the export. All the non-primary repos have long since mov…

You can use the API to export all of the metadata in a single request: https://docs.github.com/en/rest/migrations/orgs#start-an-org... https://docs.github.com/en/rest/migrations/orgs#download-an-... Using a Github App you get 15K requests per hour. Even with pagination(100 records per request) you should be able to get at all of this data within a couple of hours. I suspect you lack reliable transformation tools to t…

Thanks, yeah. We have started to look at that alternative endpoint, but it doesn't have the exact data as the api, nor is it always in the exact same format.

Although as I have run the migration myself several times to attempt to debug issues, it takes over 24hours due to ratelimiting.

Disclaimer: I'm one of the members of the technical oversight committee of the Gitea project, and am employed to work on Gitea.

Re: Blender moves from Phabricator to Gitea

#35

Post by jacooper »

rcarmo wrote: post #25
shapefrog wrote: post #11

Gitea really really really looks like github.

I use it at home and for projects with a closed user group. It does everything we need, including CI (I have Drone setup). Very, very, very good for such a small binary.

Looking forwards to gitea Actions, Drone can fall apart in advanced workloads.

Re: Blender moves from Phabricator to Gitea

#36

Post by bastardoperator »

techknowlogick wrote: post #34
bastardoperator wrote: post #32

Earlier quoted context omitted.

You can use the API to export all of the metadata in a single request: https://docs.github.com/en/rest/migrations/orgs#start-an-org... https://docs.github.com/en/rest/migrations/orgs#download-an-... Using a Github App you get 15K requests per hour. Even with pagination(100 records per request) you should be able to get at all of this data within a couple of hours. I suspect you lack reliable transformation tools to t…

Thanks, yeah. We have started to look at that alternative endpoint, but it doesn't have the exact data as the api, nor is it always in the exact same format. Although as I have run the migration myself several times to attempt to debug issues, it takes over 24hours due to ratelimiting. Disclaimer: I'm one of the members of the technical oversight committee of the Gitea project, and am employed to work on Gitea.

Create more GitHub Apps. If you're hitting rate limits you can double your capacity by adding a new app and using round robin to cycle through requests/tokens. If you're using a PAT, you only have 5k requests and will bottleneck quickly.

Re: Blender moves from Phabricator to Gitea

#37

Post by azeemba »

lucideer wrote: post #20

This is an interesting move in the context of the recent kerfuffle around Gitea - context: https://news.ycombinator.com/item?id=33749757 I wonder whether this was part of discussion on the migrating within the Blender team or whether their migration just started before the Gitea org-change. --- Off-topic but it's also funny that the Phabricator fork is Phorge & the Gitea fork is Forgejo...

The decision to move to gitea was made before that announcement.

I wonder if gitea decided to become a company after they saw the interest from Blender. I know blender folks were asking questions about the long term future of the project.

For reference, here are threads asking for proposals on solutions to consider and announcement of gitea being picked:

- https://devtalk.blender.org/t/developer-blender-org-call-for...

- https://devtalk.blender.org/t/developer-blender-org-choice-f...

Re: Blender moves from Phabricator to Gitea

#38

Post by aidenn0 »

sublinear wrote: post #22

Not to dunk on Phabricator, but did anyone actually enjoy using it? I always thought it was a mess anyway. Jenkins was also... "jankins". Of course this is all hindsight, but wow it doesn't even seem that long ago.

Phabricator's code-review (particularly if you're stuck on SVN) and ticket workflows were both great. Had both a decent command-line and decent web client. A lot of other things were a mess.

Re: Blender moves from Phabricator to Gitea

#39

Post by aidenn0 »

stryan wrote: post #7
cowmix wrote: post #2

I wonder how Gitea will hold up to all the traffic? Even Gitea hosts their stuff on Github.

I don't believe Gitea is hosting on Github for traffic reasons but for feature completeness. Relevant issue is here[0]. [0] https://github.com/go-gitea/gitea/issues/1029

Looks like https://github.com/go-gitea/gitea/pull/18165 is the last missing checkbox...

Re: Blender moves from Phabricator to Gitea

#40

Post by cturtle »

sublinear wrote: post #22

Not to dunk on Phabricator, but did anyone actually enjoy using it? I always thought it was a mess anyway. Jenkins was also... "jankins". Of course this is all hindsight, but wow it doesn't even seem that long ago.

I did! I did the Google Summer of Code twice with Blender and ever since I find myself preferring the patch workflow of Phabricator over the merge/pull request found elsewhere. I am comfortable with both, but phabricator just clicked with me better
Post reply on HN