moby--moby/pkg
Daniel Nephin 6be0f70983 Automated migration using
gty-migrate-from-testify --ignore-build-tags

Signed-off-by: Daniel Nephin <dnephin@docker.com>
2018-03-16 11:03:43 -04:00
..
aaparser
archive Automated migration using 2018-03-16 11:03:43 -04:00
authorization Automated migration using 2018-03-16 11:03:43 -04:00
broadcaster
chrootarchive
containerfs
devicemapper
directory
discovery
dmesg
filenotify
fileutils Automated migration using 2018-03-16 11:03:43 -04:00
fsutils
homedir
idtools Automated migration using 2018-03-16 11:03:43 -04:00
ioutils Automated migration using 2018-03-16 11:03:43 -04:00
jsonmessage Automated migration using 2018-03-16 11:03:43 -04:00
locker
longpath
loopback
mount
namesgenerator
parsers
pidfile
platform
plugingetter
plugins Automated migration using 2018-03-16 11:03:43 -04:00
pools Automated migration using 2018-03-16 11:03:43 -04:00
progress
pubsub
reexec Automated migration using 2018-03-16 11:03:43 -04:00
signal Automated migration using 2018-03-16 11:03:43 -04:00
stdcopy
streamformatter Automated migration using 2018-03-16 11:03:43 -04:00
stringid
symlink
sysinfo Automated migration using 2018-03-16 11:03:43 -04:00
system Automated migration using 2018-03-16 11:03:43 -04:00
tailfile
tarsum Automated migration using 2018-03-16 11:03:43 -04:00
term Automated migration using 2018-03-16 11:03:43 -04:00
truncindex
urlutil
useragent
README.md

README.md

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

Utility packages are kept separate from the moby 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 Moby 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!