Anything you change/contribute/pr there can be brought back across, and I guess those that prove themselves exceptionally competent will eventually wind up with direct access to the Gitea version.Īlso I suppose I'd better actually go slap a license on stuff or something. I might have to track it down and have some words with the people that run it and see.įork and work against the repo on github. I'd be hesitent to tie our actual working base repo there, but as an outlet for public code releases it would probably work. I think somebody is actually running a massive public gitlab instance for ~adult games~ that I can't remember the name of now. There's a new TiTS repo on github expressly for the public code releases now, and should Github deign to delete/restrict/ban that repo, then we'll move to somewhere else. What we're going to do is push out code as part of the build process to other service(s). Basically, the Gitea instance ensures we can always work on the game with minimal interruptions from providers of the hosting service. At first I was considering managing a private and a public repo there, but considering the size of the TiTS repo, I don't want to have to handle all the storage requirements for forks. The Gitea instance will likely never be public. Tl dr theres a fork that has an actual team behind it that seems to be moving faster than GOGS called Gitea - at the very least it wasn't busy falling on its face handling teams, so it's what I've ended up using. One guy is acting as overlord of maintaining the codebase and whilst I was playing around with it, the latest release failed to handle teams/groups properly. GOGS got looked at and fired out of a cannon. The public version of the repo should be anonymously accessible, just as things were on Github. Disclaimer: this post and the subject matter and contents thereof - text, media, or otherwise - do not necessarily reflect the views of the 8kun administration. I'm still investigating automation tools to assist us going the other way, so everything isn't reliant on my-and-mine-alone knowledge of Git tooling.Īs part of this, actually asking for Github access will mostly be irrelevant. Ah yes, Ive read something about the source code on one of the sticked threads. Trials in tainted space and Corruption of Champions are pretty gay. Part of our automated build process will push changes from the private repo to the public one whenever we do a public build. TiTS' source is going to be broken into two versions a public repo and a private repo. We're moving away from Github, almost certainly, to a self-hosted instance of Gitlab. Smashing the Privacy button is a quick-fix in the face of that, mainly to ensure we buy ourselves as much potential time as possible whilst we sort an alternative. We've probably been toeing a line all these years by having the source on github period, but having it placed front-and-center in the public eye was going to earn us the boot sooner or later.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |