That's a good question. Here's my attitude:
* I'm making my changes mergeable to Steffen code base. Ideally, I would love to see it merged.
A careful reader might notice that this goes a bit against Steffen-s general direction of development being centralized. At the same time, some distributed development tools simply did not exist back there at 1999. So maybe it's OK to introduce a git-based version now.
* I do not want big game changes because it takes a very good game designer to do it correctly.
Not every rule is a good one. Steffen proved to be a good person to design that. I would rather make "propositions" for rules, like I did with cost-based experience. These can be merged or NOT merged.
And finally another proposition that I planned:
* auto-patrolling territories with railroad. Currently, you may have a city with a couple of adjacent railroads. But each turn an enemy may move closer to your city. You may want to check that, move your unit to the edge of the railroad and see what's there in the fog of war. Bu-u-ut, that's micro-management again.

A VERY boring one. So, how can we fight that?
1. We may have an auto-patrol feature for units, but this is hard to maintain.
2. We may do auto-patrolling for countries that have Shinkansen Express.
3. We may just give auto-patrolling for all countries and their railroads for free. Just accept the fact that railroad gives observation -- and that's all.
This is a game rules proposition currently, no implementation "attached"...
Thoughts?...