You are reading a single comment by @MrDrem and its replies.
Click here to read the full conversation.
-
I've been looking for a project to work on, and to properly learn a language that feels like there's a point to me doing it, rather than learning it for the sake of learning it.
As such, if I want to help out and contribute to the project in future, does this mean that I should therefore be looking to get myself up to speed with Go?
MrDrem
Velocio
Today, it's best just me doing it.
We built it as a platform, optimised for how it would need to run and grow. It wasn't optimised for how easy it would be to spin up and run a local development environment.
Needless to say, if you want to start work on it... it's a bitch to get running locally (even though we have provided a repo with Vagrant and some instructions).
What I'm currently doing is tidying up the Go code so that I can move the Django logic into Go. This will take a few months... but the outcome should be that it will be extraordinarily easy to build and run locally, which means it will also be really easy to work on and contribute to.
I'm happy to talk you through code, to give lessons on how it works, etc. But today it remains difficult to just get working on it, as it's difficult to run a dev environment.