moby--moby/pkg
Lorenzo Fontana 0ecba1523d
Merge pull request #38422 from debayande/even-more-names-redux
Makes a few modifications to the name generator.
2019-01-23 02:09:52 +01:00
..
aaparser
archive pkg/archive: add TestReexecUserNSOverlayWhiteoutConverter 2018-12-11 07:18:37 +09:00
authorization
broadcaster
chrootarchive
containerfs
devicemapper
directory
discovery
dmesg
filenotify
fileutils Remove duplicated words in pkg files 2018-10-05 22:32:14 +08:00
fsutils
homedir
idtools
ioutils
jsonmessage
locker
longpath
loopback
mount Fix some go_vet issues 2018-12-19 23:57:06 +01:00
namesgenerator Makes a few modifications to the name generator. 2018-12-23 10:22:28 +00:00
parsers Skip kernel-memory tests on RHEL/CentOS daemons 2019-01-04 13:27:46 +01:00
pidfile
platform
plugingetter
plugins Remove duplicated words in pkg files 2018-10-05 22:32:14 +08:00
pools
progress
pubsub
reexec
signal pkg/signal.TestTrap: use a subtest 2019-01-12 18:04:44 +01:00
stdcopy
streamformatter Remove duplicated words in pkg files 2018-10-05 22:32:14 +08:00
stringid
symlink
sysinfo use empty string as cgroup path to grab first find 2018-12-07 18:44:00 +01:00
system Fix some go_vet issues 2018-12-19 23:57:06 +01:00
tailfile Use assert.NilError() instead of assert.Assert() 2019-01-21 13:16:02 +01:00
tarsum
term
truncindex fixes display text in Multiple IDs found with provided prefix 2018-09-24 12:17:31 +08:00
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!