Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
Hi all! I've noticed over a long period of time that the excessive amount of repositories that Azul3D has is quite confusing for new users. Additionally, our versioning scheme does not match other Go packages and has been a huge source of confusion for users as well.
How it's caused us trouble
We've also been dealing with this issue in various ways for a long time:
And also not listed above, is the high development cost on me personally to ensure that we are keeping repositories in-sync with one another. Changes to azul3d.org/gfx.v2 require changes in a separate repo at azul3d.org/keyboard.v2, we must use govers etc. to update version numbers, and it's all quite confusing for newcomers.
What the future looks like
Installing git-lfs is actually very useful outside of Azul3D, too. If you're doing gamedev, you will not want to commit your assets to your repository in order to avoid the size growing outrageously each time you modify an asset. And it's very easy to install:
OS X (requires brew install):
Windows (requires choco install):
This is definitely moving in the right direction, and while we don't know yet of all the hassles it will create, it certainly solves a number of long-standing issues with the old repo management.
Specifically, I approve of dropping the use of versioned import paths. They have caused much more pain than that created by the potential problems they may have been set out to solve.
I'll dig in a bit deeper in the next month or so, when I start to get more time on my hands.
Until then, best of luck and thanks for keeping us up to date :)
Another potential downside to the merge of all repos into a single repository is that it decreases the granularity with which permissions may be distributed to developers and contributors of Azul3d.
In the previous setup, my brother and I had read/write access to the audio repositories of the Azul3d GitHub organization. Now, I can no longer close audio related issues, which creates an unnecessary administrative overhead that I have to ping @slimsag each time (e.g. #79 (comment), #76 (comment) and #71 (comment)).
Any thoughts on how we may resolve this without giving contributors to Azul3d full access to the entire project?
This was originally added for semver-using azul3d.org packages. After azul3d/engine#1, they've all moved into a monorepo that no longer uses semver: > ### What the future looks like > > - No more package versions. So it's no longer necessary for most azul3d.org packages. The only remaining package that needs this is the semver package itself, which is not enough reason to keep this here (a single package that is not actively developed). See 2e0d1ee#commitcomment-19066368 for context. /cc @slimsag