Python Open Source Project Setup Help?

Python Help
1

Hi, I’m trying to create a game that’s open source, like Super Tux, or Super Mario War in how they’re able to be modified by anyone, and are popular enough that people actually contribute to the projects. My game is a lot more niche being a clone of a popluar-in-japan mech (giant robot) game called Gundam VS Gundam. I’ve been programming for 20 years now, but I’ve mainly done solo projects, and I’m still new-ish to python.

I’ve created a github account and added a repository for my game, but I know my coding practices aren’t nearly as good as they use to be the first 3 years of my coding life, lol. I’ve got comments I need to add, and variable names to create instead of using single letter names, but

My real question is: How do I “market” a FOSS/FLOSS/MIT project in a way that people will want to support it? Where do I even go? What license should I use? Should I go full CC0? I figured here would be the best place to start.

My game GitHub: GitHub - 0xPRIMEgs/turtle_exvs: A 2D Gundam VS Gundam style game made in python.

PS: Should I wait until I have a “1.0” to do any of this? The game is very incomplete right now.

2

That’s quite fun - nice one. I had to change screen.blit(arena) to screen.blit(arena, (0,0)).

image
image639×504 93 KB

I’d package it as an application, and add some basic install instructions too (e.g. uv tool install turtle_exvs). I’m not sure many gamers want to manually install pygame and unzip the zip file next to main.py. And put what the controls are somewhere.

I’d host the binary zip file of images etc. as a Github release instead of tracking them in Git, and in pyproject.toml use something like this to include them in the package as static artefacts.

1 Like
3

Hi, James, and thank you for the reply.
I seen your fork commit request thing, and tried to “accept” it, but I’m not sure if I did it right. I ended up removing the arena image from the code as it was a piece of old code.

I think I setup uv properly, but I’m not 100%. The assets are currently just uploaded on github now in a sub directory instead of a .zip. I’ll try looking into the static artefacts stuff, but a quick glance made it look complicated lol.

1 Like