It's possible. I probably won't do an Allegro one (unless I become interested in it at some point), but if you want to make an Allegro version, you can do so. In the releases directory, there's a download called "sge-spec". This is basically the template I used to develop the Pygame SGE, containing the basic structure and docstrings that explain all the functionality. All that needs to be done is for the functionality to be added and for a license to be chosen and applied.
ok, i will wait Pyglet backend, please send me message, when it is done.
I haven't started on that and won't start on it for a while (if at all; given the rate of development Pyglet seems to have, it seems PySDL2 has more of a future). Is there any particular reason you want to wait for a version of the SGE that uses Pyglet? Keep in mind that it would be compatible with the Pygame SGE; it's the same API.
But I wonder what you mean with more stuff than GitHub? GitHub allows for easy pull requests and a lot of other features.
Mostly the more advanced bug tracker, the web hosting, and the file hosting. I think GitHub has basically closed the gap now, but the main reason I use Savannah instead of GitHub is the philosophical one.
I would commit to both the Savannah repo and a GitHub repo if I thought it beneficial, but there were never many contributions even when GitHub was the main repo (and the few there were mostly just corrected small typos). Besides, the main thing I could use help with is testing (people putting the engine to use and reporting bugs), not development.
Maybe it would be better if he, or somebody else, changes that page? Especially since it comes up third on Google when you search for Stellar Game Engine.
Huh, that's odd. I guess I'll have to do something about that, then...
EDIT: That page now points to the SGE homepage. That should fix the problem.