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

41–50 of 58 posts

Re: Blender moves from Phabricator to Gitea

#41

Post by thcipriani »

Makes me wonder what all the other users of phab are doing. I know: twitter, dropbox, freebsd, and mozilla were all using it in some point.

I think haskell moved to GitLab, now Blender's on Gitea.

I'm curious if people are moving to phorge?

Wikimedia still uses phab for bug tracking. Taking a look at phorge Soon™

Re: Blender moves from Phabricator to Gitea

#42

Post by techknowlogick »

bastardoperator wrote: post #36
techknowlogick wrote: post #34

Earlier quoted context omitted.

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.

I.... uhh... can't say I tried that... as it's against the TOS... cough All joking aside, they have banned accounts from other projects attempting to do the same, so if I were to do that (and I'm not saying that I would), I'd want to make sure that the exporter is solid prior to risking any account.

Re: Blender moves from Phabricator to Gitea

#43

Post by thaumaturgy »

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 loved it: the code review system, integrated wiki (despite its custom markdown syntax), integrated kanban, remote repo sync, and the ability to easily and cleanly link everything together. It had its warts but I haven't yet found a single system that does everything that it did well. I know Phorge exists, but it seems to be struggling to get traction, maybe because it appeared just slightly too long after everyone had accepted Phabricator's demise.

Re: Blender moves from Phabricator to Gitea

#45

Post by techknowlogick »

cturtle wrote: post #40
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

What was your experience like with GSOC? Gitea has applied to it this year, and are hoping to be able to make it a good experience for any contributor that is matched (hopefully we are accepted as well).

Re: Blender moves from Phabricator to Gitea

#46

Post by aseipp »

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.

Yes, I absolutely loved Phabricator, and still do, even if I don't run my own instance anymore. The code review it offers is still excellent since it's based around stacked diffs, and it had some nice little extras like coverage support, first-class test results from the build reports, etc. The issue tracking is still miles ahead of GitHub and was quite flexible. It had good support for permissions and access levels, and tools like Herald were very useful. Evan also had a very keen eye for many things design wise, and was fun to chat with. I think a lot of the things it did it did very well.

But there were definitely some scope issues and other stuff that could have been handled better. It's hard to keep up with GitHub now that they're pretty aggressive about features, etc. But the core competencies have always been very good in my opinion, and it has a nice, hackable codebase.

Re: Blender moves from Phabricator to Gitea

#47

Post by slondr »

vidanay wrote: post #18
lucideer wrote: post #14

Earlier quoted context omitted.

That's a great ticket, & also links to a really nice & insightful comment from one of the Fog Creek folk https://lobste.rs/s/gokjbo/gitea_1_1_0_released#c_dg9pwe

I still dream of a world where FogBugz & Kiln gained the respect they deserved. Mercurial was pretty damn nice.

Was? It still is very nice.

Re: Blender moves from Phabricator to Gitea

#48

Post by phailhaus »

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.

The way it handled branches and merging was an absolute nightmare. IIRC it did this super weird thing that when you put up a diff from the CLI, it made its own little temporary branch for you. And god forbid if you pushed up your branch remotely, it would get all confused and start diffing against that remote branch. Literally couldn't merge via the UI, the CLI was the only way.

To be fair, the review system was better than GitHub. It's insane that even today, there's no way to tag your team and have them stay tagged. If anybody comments or reviews, they're dismissed. This is an issue that's been open for nearly five years. [1]

[1] https://github.com/community/community/discussions/5289

Re: Blender moves from Phabricator to Gitea

#49

Post by tylersmith »

bawolff wrote: post #16
tylersmith wrote: post #9

Earlier quoted context omitted.

Gitea does not use Github because the software can't handle their load requirements, but because they started using GH before Gitea had all the features they needed. They are actively working on hosting Gitea on Gitea, with the last piece being an importer to move over all their GH data. Blender seems to have been ok manually migrating some things and abandoning other things, since they weren't likely to ever get a P…

How much traffic could they possibly have? Quite frankly either gitea has absolutely terrible scalability or something else is off here. Edit: i misread the parent comment. My bad.

Tbf my comment was phrased a bit ambiguously, but I couldn't think of anything less ambiguous.

Re: Blender moves from Phabricator to Gitea

#50

Post by bastardoperator »

techknowlogick wrote: post #42
bastardoperator wrote: post #36

Earlier quoted context omitted.

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.

I.... uhh... can't say I tried that... as it's against the TOS... cough All joking aside, they have banned accounts from other projects attempting to do the same, so if I were to do that (and I'm not saying that I would), I'd want to make sure that the exporter is solid prior to risking any account.

It's not against the TOS, the documentation is very clear:

  "Keep these ideas in mind when creating GitHub Apps:

  - A user or organization can own up to 100 GitHub Apps."
https://docs.github.com/en/developers/apps/getting-started-w...

Which is 1.5 million API requests per org per hour.

Post reply on HN