Exploring a possibility of GitHub speculative biology database of sorts

I broke through to post this so:

Some time ago I was reading

and idea of speculative biology database appeared in my head. GitHub let’s people remotely propose changes to a filesystem (also lets create versions of said filesystem), so why not combine these two things together?

I could theoretically already make it myself, but it would probably soon be forgotten by me, etc…

So here I wanted to discuss this idea. First of all, the filesystem structure.
My idea was to split database into location folders that would have their time folders, era folders perhaps, like this:

Folder
Planet Alpha
Years 0 - 1000 Prelife Era

Data

Years 1000 - 5000 First Era

Data

Planet Beta
Years 0 - 1000 Prelife Era

Data

Years 1000 - 5000 Newborn Era

Data

Inside era folder there could be the species present on a planet in that period of time. These species could also be located in some folders that would categorize them maybe?

Planet folder perhaps could have some miscellaneous data files.

Then, if new era occurs, previous era folder is duplicated, renamed, and species in it are changed (or not changed). If a species that was in previous era is not present in new era, that means it has gone extinct.

Planet Alpha
Years 0 - 1000 Prelife Era

Species 1: small

Planet Alpha
Years 0 - 1000 Prelife Era

Species 1: small

Years 1000 - 5000 First Era

Species 1: large

This could be a nice time-killer for when someone is bored. I have more ideas in my head but I’m going to wait for your opinion.

Also, if you are familiar with GitHub and programming I suggest to contribute to Thrive, it is worth it :slight_smile: (There may be a high probability you already were considering it, but anyways.)

2 Likes

I feel like it be cooler if time is showed by commit kind of like Historical Edits of the USA Constitution repository since it allow you to diff changes and other cool things. It would also just make sense to make time be time. Though it would require the person to manage the repository to have some git-fu knowledge.

The commit should also have some special formatting if we do that though.

Maybe you could some interesting things with different branches but I am not entirely sure what yet…

1 Like

Or the people contributing would need to follow good git practices like sensible commit messages and splitting up their work into separate commits. It’d be a ton of work for a single person to try to fix the mess everyone sends in if everyone was allowed to just dump huge changes all bunched up into a single commit.

1 Like

Prototype:

Most stuff is not on main branch, but on branch_1.

I don’t know if the license I chose was a good idea, but anyways.