The Arc-F fork brought up the issue that people don't know how to create public git repositories. I'm not completely sure, but I have good circumstantial evidence that I can do it. I made two new git repositories, one with "git init", and one with "git init --shared", and looked at the .git/config files they produced. As far as I can tell, you need to go into your .git/config file, and in the "[core]" section, add a line that says "sharedrepository = 1". You might also be able to get the same effect with the "git config" command. You will also have to set the permissions on everything in your git repository so that everyone can write to them (chmod a+rw, I think). There's stuff on this in the git-config manual page at http://www.kernel.org/pub/software/scm/git/docs/git-config.html, the git-init manual page at http://www.kernel.org/pub/software/scm/git/docs/git-init.html (look at the --shared option), and the git user's manual at http://www.kernel.org/pub/software/scm/git/docs/user-manual.html (see chapter 4, Sharing Development). None of these completely document what you need to do, but I think you can piece together some information. If that works, the next question will be how to manage development with separate repositories. I suggest we have one repository with pure implementation-independent Arc code, and then a repository for each implementation (assuming people don't like the single-repository model). If someone can figure out how git-submodule works, the implementations could then all include the pure Arc code as a library module, so they would all get whatever updates were pushed to that automatically. So, will someone try this and see how it works? If not, we can troubleshoot it. And if it does, we should probably discuss the development setup. |