Actually I think that the github wiki uses the markdown format (which is still pretty simple.

You put the instructions on the Github wiki, and you detokenize your source to a .axe file with the scripts I'll (or Pimath will for Windows) provide then you add it in the project folder and click commit in the Github app. Add a comment, then sync. Boom, you just uploaded your work and everybody can access it.

Update : I can confirm that resending an OS (2.43) and reapplying all my patches except this one fixes the issue with Axe.

Non issues:
-git: There's a.Windows app for github for those who don't know how to use it, for pimath: what willrandship said.
-On calc coding: no real problem here but you'll have to detokenize your stuff and merge or overwrite it in git.

Virtualbox is a real problem though. If I can figure out this batch scripting bullshit. then it's not.gonna be necessary but you'll still need tilem and optionallly tilp.

Oh yeah that looks pretty good. Nice job Eiyeron.

Okay so I'm deciding how the team work will be organized since it looks like I'm recognized as lead dev.

-All the (re)source, build scripts, etc. will be hosted on Github.
-Shmibs's tok8x will be used to tokenize Axe code which will be stored in raw text files with .axe as extension.
-SPASM will be used for all Asm code (which will e compiled as Axioms) and resource file generation.
-Sprites should be stored as 8x8 or 16x16 BMPs since we use SPASM.
-Code formatting conventions should be established.
-When working on something, contributors would do their thing in a new branch which I'll approve before merging to master.
-I'll write some scripts (GNU make based) to compile Axe code in an emu (tilem2) and then run it either in emu or on an attached hardware calc. This will make testing easy and convenient for everyone.
-Every contributor shall be able to build binaries in order to test (including spriters and mappers). This means that at least a Linux virtual machine is required. I can cook up a VirtualBox image with all the dev environment set up if needed.

Anything to add / ammend ?

Yeah. To explain how slow the TI-OS one is, it is often used as a replacement to For(Z,0,25:End to save a few bytes. I got the idea for an xLIB one only after noticing the rectangles were a little slow-ish, though.

Lol ? That's awful !

5556: You explore kilometers of corridors in your new school desperately looking for the library in an urge to get on Omni. (true story)