Spring RTS Engine

Currently infrastructure mostly "just works", but there could be a lot of things improved.

I've started a wikipage to hopefully organize information a bit better:

https://springrts.com/wiki/Infrastructure:Development

On my wish list are A LOT of things, but sadly i don't have the time to implement these.

For a TODO, see the issue trackers of the dedicated projects.

Has somebody ideas about how to make contributing to these projects more interesting / easier?

Any important question(s) which needs to be answered at the wiki page?

Definition infrastrucure:
- everything needed for running online games (=lobby server, lobby clients, download systems, website, replay website, ...) but not the spring engine itself!

I've updated the page, and I think we should consider adding/linking lobbyserver/client links as well as skirmish and (future) matchmaking bots.
What else would do you think would fit there? Replay site, analytics, etc.?

PS: I'm wary of adding pages that won't be actively updated

gajop wrote:PS: I'm wary of adding pages that won't be actively updated

i agree with that. i mostly want just some "overview" page, where the important services are listed, so mostly a link collection with small descriptions.

I did look at the trackers and they seemed like mostly minor issues to me. What sort of things were you thinking of on your wishlist? My general feeling is that our infrastructure works well & the last remaining "big thing" needed for fully functional single player is in-engine downloads.

Silentwings wrote:I did look at the trackers and they seemed like mostly minor issues to me. What sort of things were you thinking of on your wishlist? My general feeling is that our infrastructure works well & the last remaining "big thing" needed for fully functional single player is in-engine downloads.

yeah, it works mostly well. my wishlist is stuff like:

- merge springfiles / replay.springrts.com codebase: uploads of maps/games/engine/... can be automated and the deprecated code can be removed (drupal 6 is used which isn't maintained any more)
- replace polling code with events
- refactor upq's code so the search api can be used at all mirrors
- add full support to rapid
- refactor/improve lobby server code
- simplify stuff / make code more generic
- migrate code to python3+

so no big things, mostly refactors / code cleanups.

Split feature requests to viewtopic.php?f=21&t=33810, this topic is a request for help, not for more work!

Split removing engine macros question to viewtopic.php?f=71&t=33814.

I'm hacking on a matchmaking bot right now, but I'd be glad to pitch in to more infra-y stuff once a draft of the matchbot is ready for initial usage. I'll poke you on IRC, abma, so we can chat about priorities and good starter projects.

the problem still exists, i feel basicly alone on the infrastructure front. help is really needed for the infrastructure maintainance.

i.e.
- the webpage still isn't updatet to the current version
- the same for the lobby server


also the negative feedback even on suggestions for improvements really demotivates me of doing anything, i miss some JFDI atmosphere in community.

(adjusted topic tile)

I'll be back to infra (mm) from around May/June

FYI: I gave TurBoss root permissions on the springrts.com server. So he can hopefully help with problems/issues/development, too.

Welcome as admin!

Thx to the dev team for trust me

i'll do my best

if anyone is in against i'll drop my rights

thx again

He pushed dick shaped units into the journeywar repo. How dare you TurBoss

I started an admin category in the wiki which hopefully helps with some common tasks: https://springrts.com/wiki/Category:Administration