just watching humanity burn hard-earned resources on something arguably worse than arms race and dotcom/blockchain craze combined. Got to outlast it, in spite.
Even worse when you want to contribute to some key project that likely won’t leave Github (issue being Copilot training). In my case it’s Godot bindings in my preferred (somewhat niche) language. I already contributed an example and have another better example I haven’t uploaded because of this (other issues though too, so I haven’t even been able to share an export).
Well at least with opensource, we can keep forking. Like Audacity project showed is possible, for example, through chaos to better product. I’m more concerned with physical resources though, those do not fork.
Github is not git, after all, and self-hosting some git server is kind of simple. Not doing it myself though, too many friends who do it already lol.
This isn’t really a ‘fork it’ type of problem. Closest to that I can viably do is just have my project elsewhere (gitlab or codeberg, or even just uploaded to itch) and allow the bindings project to link to it. Even then, it could still be scraped one way or another.
I don’t really understand enough to improve the bindings code itself and the project only currently has 4 other contributors (and those likely aren’t anywhere close to half-as-much as the creator), so the idea that moving would harm said project definitely is valid.
Godot itself is large enough that it could survive a move, though it’s likely too complicated with all existing things (unless they split out for ultra-future 5.X?). I do know that worse people (maybe-or-maybe-not better coders) have tried to fork Godot with the long-term outcome likely not being noteworthy.
just watching humanity burn hard-earned resources on something arguably worse than arms race and dotcom/blockchain craze combined. Got to outlast it, in spite.
Problem is not wanting your creations scraped.
Even worse when you want to contribute to some key project that likely won’t leave Github (issue being Copilot training). In my case it’s Godot bindings in my preferred (somewhat niche) language. I already contributed an example and have another better example I haven’t uploaded because of this (other issues though too, so I haven’t even been able to share an export).
Well at least with opensource, we can keep forking. Like Audacity project showed is possible, for example, through chaos to better product. I’m more concerned with physical resources though, those do not fork.
Github is not git, after all, and self-hosting some git server is kind of simple. Not doing it myself though, too many friends who do it already lol.
This isn’t really a ‘fork it’ type of problem. Closest to that I can viably do is just have my project elsewhere (gitlab or codeberg, or even just uploaded to itch) and allow the bindings project to link to it. Even then, it could still be scraped one way or another.
I don’t really understand enough to improve the bindings code itself and the project only currently has 4 other contributors (and those likely aren’t anywhere close to half-as-much as the creator), so the idea that moving would harm said project definitely is valid.
Godot itself is large enough that it could survive a move, though it’s likely too complicated with all existing things (unless they split out for ultra-future 5.X?). I do know that worse people (maybe-or-maybe-not better coders) have tried to fork Godot with the long-term outcome likely not being noteworthy.