moby--moby

History

Brian Goff 29dbcbad87 Merge pull request #22925 from jstarks/fix_integration_test pkg/integration: Port tests to Windows		2016-05-24 17:31:43 -04:00
..
aaparser	apparmor: fix version checks to work properly	2016-02-15 20:36:07 +11:00
archive	fix typos	2016-05-06 18:23:11 +08:00
authorization	pkg: authorization: cleanup tests	2016-05-08 14:18:38 +02:00
broadcaster	…
chrootarchive	pkg: chrootarchive: chroot_linux: fix docker build	2016-05-10 00:42:49 +02:00
devicemapper	…
directory	Get the Docker Engine to build clean on Solaris	2016-05-23 16:37:12 -07:00
discovery	Use net.JoinHostPort to handle address format.	2016-03-01 17:27:30 -08:00
filenotify	add file poller panic fix from 1.10.2	2016-02-24 10:17:29 -05:00
fileutils	Get the Docker Engine to build clean on Solaris	2016-05-23 16:37:12 -07:00
gitutils	Windows CI: Unit tests - port pkg\gitutils	2016-02-11 18:19:17 -08:00
graphdb	Windows CI: Turn off failing unit tests pkg\graphdb	2016-03-02 19:27:41 -08:00
homedir	Revert "resolve the config file from the sudo user"	2016-02-29 13:51:43 +01:00
httputils	Fix some typos in comments and strings	2016-02-22 20:27:15 +01:00
idtools	Lazy init useradd and remove init()	2016-04-06 17:53:45 -04:00
integration	pkg/integration: Port tests to Windows	2016-05-24 12:12:48 -07:00
ioutils	Fix concurrent map access in bytespipe	2016-05-12 10:04:05 -04:00
jsonlog	Add support for reading logs extra attrs	2016-05-06 20:42:20 -04:00
jsonmessage	…
listeners	Get the Docker Engine to build clean on Solaris	2016-05-23 16:37:12 -07:00
locker	…
longpath	…
loopback	…
mflag	…
mount	Get the Docker Engine to build clean on Solaris	2016-05-23 16:37:12 -07:00
namesgenerator	Adding Rita Levi-Montalcini and Claude Shannon to name generator	2016-05-04 00:14:09 +05:30
parsers	Get the Docker Engine to build clean on Solaris	2016-05-23 16:37:12 -07:00
pidfile	Windows: don't overwrite PID file if process exists	2016-04-18 16:41:37 -07:00
platform	Get the Docker Engine to build clean on Solaris	2016-05-23 16:37:12 -07:00
plugins	When calling volume driver Mount, send opaque ID	2016-04-29 09:37:02 -04:00
pools	fix variables that werent being called	2016-03-17 13:19:55 -07:00
progress	…
promise	…
proxy	pkg/proxy: remove unused 'transfered' variable	2016-05-10 14:33:21 -07:00
pubsub	Revert "use pubsub instead of filenotify to follow json logs"	2016-02-23 21:43:52 -05:00
random	…
reexec	Get the Docker Engine to build clean on Solaris	2016-05-23 16:37:12 -07:00
registrar	fix typos in pkg	2016-04-09 21:18:15 +08:00
signal	Get the Docker Engine to build clean on Solaris	2016-05-23 16:37:12 -07:00
stdcopy	Optimizations for StdWriter	2016-03-25 22:14:27 -04:00
streamformatter	Fix flaky test TestJSONFormatProgress (#21124 )	2016-03-14 16:00:12 +00:00
stringid	fix typos in pkg	2016-04-09 21:18:15 +08:00
stringutils	fix typos in pkg	2016-04-09 21:18:15 +08:00
symlink	fix variables that werent being called	2016-03-17 13:19:55 -07:00
sysinfo	Get the Docker Engine to build clean on Solaris	2016-05-23 16:37:12 -07:00
system	Get the Docker Engine to build clean on Solaris	2016-05-23 16:37:12 -07:00
tailfile	…
tarsum	Fix build cache false positives when build context tar contains unnormalized paths	2016-04-14 17:57:45 -07:00
term	Windows: Turn on native console by default	2016-05-20 19:19:26 -07:00
tlsconfig	…
truncindex	pkg: truncindex: provide more info in error	2016-03-17 15:53:12 +01:00
urlutil	Support unixgram syslog address	2016-04-28 11:04:50 +08:00
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!