moby--moby/pkg
Jess Frazelle bf892efe36 Merge pull request #16405 from michaelhuettermann/master
Adding another scientist to the hall of fame.
2015-09-18 16:09:01 -07:00
..
ansiescape
archive Windows: Fix long path handling for docker build 2015-09-15 10:58:11 -07:00
broadcastwriter
chrootarchive Windows: Fix long path handling for docker build 2015-09-15 10:58:11 -07:00
devicemapper
directory Windows: Fix long path handling for docker build 2015-09-15 10:58:11 -07:00
fileutils Windows: Fix warning on info 2015-09-18 13:39:12 -07:00
graphdb
homedir
httputils
integration Skip racey TestDockerCmdInDirWithTimeout 2015-09-17 15:30:07 +02:00
ioutils
jsonlog
jsonmessage events/jsonmessage: add and prefer TimeNano for events 2015-09-18 13:15:26 -04:00
listenbuffer
longpath Windows: Fix long path handling for docker build 2015-09-15 10:58:11 -07:00
mflag
mount
namesgenerator Adding another scientist to the hall of fame. 2015-09-18 21:31:12 +02:00
nat
parsers
pidfile
plugins
pools
progressreader
promise
proxy
pubsub
random
reexec
signal
sockets
stdcopy
streamformatter
stringid
stringutils
symlink Windows: Fix long path handling for docker build 2015-09-15 10:58:11 -07:00
sysinfo
system
tailfile
tarsum
term Remove unused variable, fix #16310 2015-09-15 22:20:10 +02:00
timeoutconn
timeutils
tlsconfig
truncindex
ulimit
units
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!