[steinuil]

> but to have a good GitHub alternative.

JJ doesn't currently have a "native" repository format (or rather, it's in development and not ready for general usage), so right now a JJ forge wouldn't look too different from your usual Git forges.

Everybody who's using it right now uses it on Git repos on Git forges. I've been using it for months on my own and at work and I didn't make any changes to the infrastructure outside of my own command line usage.

It would be interesting to see what a JJ-native forge would even look like in the future, but I don't think anybody knows exactly what that would be right now! JJ is in development (but stable enough to work with) and people have only just started using it, so it's still in the phase of discovering what workflows are possible.

> Plus a good IDE support.

Now that's something I would love to see. Git tooling works mostly fine but due to how JJ's git backend works, it always thinks it's in a "detached HEAD" state.

[gpm]

> Everybody who's using it right now uses it on Git repos on Git forges.

As I understand it there's also a group of Googlers using it internally at Google with an internal to Google non git backend.

[v3ss0n]

i gotta try a bit then.