Clone this repo:

Branches

  1. 0a5fcd7 Some test CL v7 by Brad Fitzpatrick · 1 year, 5 months ago master
  2. 9ba773e Merge "lock: fix so it can succeed after failing" by mpl · 1 year, 5 months ago
  3. 6949c96 lock: fix so it can succeed after failing by Roger Peppe · 1 year, 5 months ago
  4. 49c9a16 README: add instruction for git commit hook by mpl · 1 year, 5 months ago
  5. 96a2350 lock: new package by mpl · 1 year, 6 months ago

TEST

go4

travis badge

go4.org is a collection of packages for Go programmers.

They started out living in Camlistore‘s repo and elsewhere but they have nothing to do with Camlistore, so we’re moving them here.

Details

  • single repo. go4 is a single repo. That means things can be changed and rearranged globally atomically with ease and confidence.

  • no backwards compatibility. go4 makes no backwards compatibility promises. If you want to use go4, vendor it. And next time you update your vendor tree, update to the latest API if things in go4 changed. The plan is to eventually provide tools to make this easier.

  • forward progress because we have no backwards compatibility, it‘s always okay to change things to make things better. That also means the bar for contributions is lower. We don’t have to get the API 100% correct in the first commit.

  • code review contributions must be code-reviewed. We‘re trying out Gerrithub, to see if we can find a mix of Github Pull Requests and Gerrit that works well for many people. We’ll see.

  • CLA compliant contributors must agree to the Google CLA (the same as Go itself). This ensures we can move things into Go as necessary in the future. It also makes lawyers at various companies happy. The CLA is not a copyright assignment; you retain the copyright on your work. The CLA just says that your work is open source and you have permission to open source it. See https://golang.org/doc/contribute.html#tmp_6

  • docs, tests, portability all code should be documented in the normal Go style, have tests, and be portable to different operating systems and architectures. We'll try to get builders in place to help run the tests on different OS/arches. For now we have Travis at least.

Contributing

To add code to go4, send a pull request or push a change to Gerrithub.

To push to Gerrithub:

See https://review.gerrithub.io/Documentation/user-upload.html for more generic documentation.

(TODO: more docs on Gerrit, integrate git-codereview?)