moby--moby/pkg
Vincent Demeester b18f9cc29b Merge pull request #20833 from Microsoft/testunit-archive
Windows CI: Unit Tests stop running failing archive test
2016-03-02 08:53:11 +01:00
..
aaparser
archive Windows CI: Unit Tests stop running failing archive test 2016-03-01 13:27:44 -08:00
authorization Merge pull request #20602 from twistlock/20508_authz_plugin_corrupt_body 2016-02-29 10:43:02 -05:00
broadcaster
chrootarchive Windows CI: Unit Tests stop running failing chrootarchive tests 2016-03-01 14:28:29 -08:00
devicemapper
directory
discovery Use net.JoinHostPort to handle address format. 2016-03-01 17:27:30 -08:00
filenotify
fileutils
gitutils
graphdb
homedir Revert "resolve the config file from the sudo user" 2016-02-29 13:51:43 +01:00
httputils
idtools
integration
ioutils
jsonlog
jsonmessage
locker
longpath
loopback
mflag
mount
namesgenerator
parsers
pidfile
platform
plugins Merge pull request #20686 from clintonskitson/bugfix/plugin_desc_leak 2016-02-29 10:44:36 -08:00
pools
progress
promise
proxy
pubsub
random
reexec
registrar
signal
stdcopy
streamformatter
stringid
stringutils
symlink Windows CI: Turning off pkg\symlink unit testing 2016-02-29 13:10:50 -08:00
sysinfo
system
tailfile
tarsum
term Merge pull request #20587 from MHBauer/termfixes 2016-03-01 11:37:26 -05:00
tlsconfig
truncindex
urlutil
useragent
version
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!