One idea I picked up somewhere: Give kids screen credit, for example 10 coins per week, each worth 30 minutes of screen time. This allows them to freely manage it (e.g. a little bit every day vs. a long Minecraft session on the weekend), while it's a clear rule and limit at the same time.
> Inability to compile Docker from source without using the Docker Project's provided "black box" binary Docker.
I also found this particular annoying.
To build it from source, make sure to install all dependencies (check the provided Dockerfile for details), add both docker and docker/vendor to your GOPATH and then execute `bash hack/make.sh dynbinary`
Yes, Git is maintained very conservative and a lot of effort is put into review and testing even before patches hit the 'pu' or 'next' branch (Git's staging branches), where they usually cook for some time before getting merged (if at all).
I even use pu on my work machine to be able to test and use the latest features and never had a serious problem.
>No. Each developer works in her private repo, for sharing work you use a bare repo people push to / fetch from
What do you mean by a "bare repo"? blhack wants to make it so that they commit code into the same repo. You could do that by setting up a repository somewhere, and then each person would clone it.
--bare ensures you don't have a working directory. It is the bare .git directory only. You don't want people pushing to your working directory. Simple as that.
You could setup a remote and each person could clone that remote.
I left out the details about what you do after you clone (push/pull), but the point was that there is nothing special about the remote repository as far as it being "bare". Which turns out isn't right. You can set up a bare repository with no working directory as 2mur has pointed out. I wonder if that is a requirement. I always thought that if you clone a repository you can just start using it as a remote without additional hassle.
> You can set up a bare repository with no working directory
A bare repository has no working tree per se.
> I wonder if that is a requirement. I always thought that if you clone a repository you can just start using it as a remote without additional hassle
You can use bare and non-bare repositories as remote, but you should use only bare repositories (unless you know what you are doing). Here's a good explanation: http://bare-vs-nonbare.gitrecipes.de/
