[CODE] Suggestion: repository with fork of mojoAL

[eri0o]

This is just a minor suggestion to keep mojoAL updates easier on the main repository. We could have a fork of mojoAL from icculus in the organization and then just rebase our changes on top of icculus main branch. In this way it would be easier to update and also to sync and track changes.

I suggest here because I don't have permission on the org to create repositories so perhaps one of the devs could do this.

[Crimson Wizard]

Is the purpose to have mojoAL as a submodule, or have our own branch of it?
I don't recall, do we still have any changes of our own that are not applied to upstream; or are any planned?

[eri0o]

I was thinking on having our own branch of it... But now I am unsure

I don't recall, do we still have any changes of our own that are not applied to upstream; or are any planned?

So in my head we had done the panning change (I have an unmerged PR there based on your work) but apparently we actually never did it or it's not in an individual commit. I don't know, need to check the code now... :/