moby--moby/pkg
Daniel Nephin a5631c75e1 Merge pull request #34613 from dnephin/remove-pkg-testutil-cmd
Remove pkg testutil cmd
2017-08-25 15:09:52 -04:00
..
aaparser
archive archive: add ChownOpts support to TarWithOptions 2017-08-23 20:52:29 +02:00
authorization Remove string checking in API error handling 2017-08-15 16:01:11 -04:00
broadcaster
chrootarchive
devicemapper Add deadcode linter 2017-08-21 18:18:50 -04:00
directory
discovery
filenotify
fileutils Add goimports to linters. 2017-08-21 18:15:08 -04:00
fsutils
homedir
idtools
ioutils Fix golint errors. 2017-08-18 14:23:44 -04:00
jsonlog
jsonmessage Fix golint errors. 2017-08-18 14:23:44 -04:00
locker
longpath
loopback
mount Add goimports to linters. 2017-08-21 18:15:08 -04:00
namesgenerator
parsers
pidfile
platform
plugingetter
plugins Add deadcode linter 2017-08-21 18:18:50 -04:00
pools
progress
promise
pubsub
reexec
signal Add test coverage to signal/trap.go 2017-08-09 15:13:38 +05:00
stdcopy
streamformatter Add goimports to linters. 2017-08-21 18:15:08 -04:00
stringid
stringutils
symlink
sysinfo
system Use event functions from golang.org/x/sys/windows 2017-08-21 12:58:09 +02:00
tailfile
tarsum
term pkg/term: set termios VMIN and VTIME in MakeRaw on Linux 2017-08-03 13:21:42 +02:00
testutil Remove pkg/testutil/cmd 2017-08-25 12:07:31 -04:00
tlsconfig
truncindex
urlutil
useragent
README.md

README.md

pkg/ is a collection of utility packages used by the Docker project without being specific to its internals.

Utility packages are kept separate from the docker core codebase to keep it as small and concise as possible. If some utilities grow larger and their APIs stabilize, they may be moved to their own repository under the Docker organization, to facilitate re-use by other projects. However that is not the priority.

The directory pkg is named after the same directory in the camlistore project. Since Brad is a core Go maintainer, we thought it made sense to copy his methods for organizing Go code :) Thanks Brad!

Because utility packages are small and neatly separated from the rest of the codebase, they are a good place to start for aspiring maintainers and contributors. Get in touch if you want to help maintain them!