I guess the benefit will be a “better overview” because you don’t have to search for repositories but can instead see them more easily.
The cost would be having 3 organizations to maintain.
Also note that jbullet is a bit special in that it is in jar form in our repository lying here: jmonkeyengine/jbullet.jar at master · jMonkeyEngine/jmonkeyengine · GitHub
In theory we should instead use that jbullet repository, maybe using git submodules or also a maven repository as intermediate.
The problem there was that we aren’t 10000% sure that the repo and the jar are in sync and that it was the final version. It would require testing and someone caring about maintaining jbullet and jme3-jbullet, which is currently not the case, though. So long it’ll only be a “mirror” or an archive (because it’s not exactly a mirror but has had our modifications to it, iirc).