Files
docker-cli/components/engine/pkg
Aaron Lehmann 56af301200 Merge pull request #27287 from mavenugo/pluginv2-sk2
Allow multiple handlers to support network plugins in swarm-mode 
Upstream-commit: 2c620d0aa24c5f774a9115449a86b158b005bba8
Component: engine
2016-10-20 13:43:04 -07:00
..
2016-10-13 13:55:38 -07:00
2016-10-19 17:46:27 +08:00
2016-06-02 17:17:22 +08:00
2015-12-13 18:04:12 +02:00
2016-06-11 13:16:55 -07:00
2016-05-26 19:28:18 -07:00
2016-08-01 22:01:20 +08:00
2016-09-16 11:56:15 -07:00
2016-10-04 12:03:29 -07:00
2016-06-23 16:09:13 -07:00
2015-12-13 18:04:12 +02:00
2016-08-10 22:56:05 +08:00
2016-04-09 21:18:15 +08:00
2016-03-25 22:14:27 -04:00
2016-10-05 14:47:15 -07:00
2016-04-28 11:04:50 +08:00

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!