The asteroids oxp was a bad choice for two simple reasons:
The asteroids oxp is one of Charlie’s oxps and Charlie is back.
Although it can stand as an independent oxp Charlie gave that oxp to little bear (a long time ago) with the permission to integrate it with asteroid storm oxp (I have always considered asteroid storm as a joined creation of little bear and Charlie).
Eric (in his good will) didn’t know that when he found it, he update it and submit it in the wiki. Now you did the same thing.
So firstly we cannot consider asteroids as an abandoned oxp and secondly now we have two oxps (the second in two versions yours and Eric’s) that do the same thing, increase the variety of asteroids in the game. I strongly recommend to pm little bear, charly and eric and cooperate with them for an advance version of asteroid storm.
For more information
https://bb.oolite.space/viewtopic.php?t=4178
Now if you want to upgrade – bug fix and optimize abandoned oxp there are a lot of them:
All murgh oxps – they are a lot of them. For starters:
1.Lave (that “CANNOT addShipsAt: 'mortran 1 pwm 13935 41730 14230' (should be addShipsAt: role number coordinate_system x y z)” is in my stderr file since the Stone Age. This oxp has at least one conflict with transports oxp
2.Transports opx
3.You may want to add custom views and shaders in all murgh ship oxps (new vipers, tug ship etc)
All 8bitapocalypse opxs. Super cobra, ixian ships (this one can take a lot of maintenance), greek ships etc
If you want to bug fix and maybe continue a mission opx
Ionics is ideal. Galileo has gone for ages and this opx is open ended.
I cannot say that Aegidian opxs are abandoned since all the community live with the hope that someday Giles will return, even as an opx writer and maintain them himself.
But keep in mind those things
1.Make sure by confirming with at least 2 elder members of the community that this opx is abandoned.
2.PM the original author and notify him for your intentions.
3.Notify the community for the oxps you want to adopt in case someone else want to adopt that same oxps with you (Yes we have such an incident very recently with Deposed)
4.Put your updated opxs in the wiki.
5.Give credit in the readme file to the original author.
I strongly recommend and support the adoption of old and abandoned oxps but without the proper organization and coordination the whole effort will bring chaos (Multiply versions of the same oxps, original authors returning and see that their opxs have taken a direction that they never want without their permission etc)