Going from 500 entries to 1000 entries in the OS games list in the last couple of weeks left me a bit drained and mentally exhausted. I realize that I need to take a couple of weeks holiday from adding entries everyday, before continuing with a couple of 100s more (LibreGameWiki and backlog) that is to be followed by validating the content and programming a better web output.
Doing the same stuff day by day drained all my free energy. Maybe the Coloring App or some other projects get a bit of love in the mean time.
Gathering information about and improving open source games.
Thursday, September 26, 2019
Wednesday, September 18, 2019
1k entries in the os games list
Today with additions from osgameclones, libregamewiki and my own backlog of places to visit, the os games list has grown to more than 1,000 entries. Not all of them are games though, there are game engines, tools, libraries as well. However, emphasis is still on growing the library and doing the reorganization later. I'm quite confident that I can reach 1.3k entries within a few weeks.
Then I will stop seeking for missing games actively, consolidate the information, work on a richer web presentation and start contributing to the projects with emphasis on the build process.
Then I will stop seeking for missing games actively, consolidate the information, work on a richer web presentation and start contributing to the projects with emphasis on the build process.
Sunday, September 8, 2019
What to do once the list of open source games is kind of settled?
It seems like at some point I will have included a good portion of the existing open source game projects in the database. I never really wanted to stop there and that will mean that I can start with the next phase soon. The question is how to do that exactly?
I imagine I could work over the games and carefully check the assets licenses, try to build them, make small fixes and sometimes even larger ones and prepare binaries as a first thing. In order to be efficient, I would group the projects by programming language, i.e. Java first, then Python, then JavaScript, then C/C++, then the rest. Also, inactive but mature projects would be preferred and I could spend proportionally more time on genres I like a lot like strategy or role playing. I would also prefer projects with free assets and the GPL license. While MIT, BSD and Apache are nice licenses they basically do not guarantee that future contributions stay that way. For some games without an active community anymore, maybe I can induce a transition to GPL, but of course only if my contributions are substantial.
We will see how it all plays out, but that's the plan so far.
I imagine I could work over the games and carefully check the assets licenses, try to build them, make small fixes and sometimes even larger ones and prepare binaries as a first thing. In order to be efficient, I would group the projects by programming language, i.e. Java first, then Python, then JavaScript, then C/C++, then the rest. Also, inactive but mature projects would be preferred and I could spend proportionally more time on genres I like a lot like strategy or role playing. I would also prefer projects with free assets and the GPL license. While MIT, BSD and Apache are nice licenses they basically do not guarantee that future contributions stay that way. For some games without an active community anymore, maybe I can induce a transition to GPL, but of course only if my contributions are substantial.
We will see how it all plays out, but that's the plan so far.
Subscribe to:
Posts (Atom)