Also added back some of the maintainer processes that were in
MAINTAINERS but moved to docker/opensource repo. I believe this
project's governance should be disconnected from docker/opensource as
project's remaining under docker/opensource will not use the Moby TSC.
Signed-off-by: Phil Estes <estesp@linux.vnet.ibm.com>
Upstream-commit: 449c870afbd21563a6df04445fbb136d3230629b
Component: engine
This largely removes references to Docker where possible.
The HOWTO guides are still Docker docs and refer to Docker not
moby, so the next step is to rework these as Moby docs and put
them in `docs/` in this repo.
Signed-off-by: Justin Cormack <justin.cormack@docker.com>
Upstream-commit: cecd0de3a9f783b34f75ca5e6394b9a0c123999e
Component: engine
This adds a new package `integration` where `engine` integration tests
should live. Those integration tests should not depends on any `cli`
components (except from the `dockerd` daemon for now — to actually
start a daemon).
Signed-off-by: Vincent Demeester <vincent@sbr.pm>
Upstream-commit: 6b025a8b665f7b976bb2560488ba07f55dbf0fb6
Component: engine
There's ~27k questions by now, not just 7k 😉
Signed-off-by: Fabian Lauer <kontakt@softwareschmiede-saar.de>
README.md & CONTRIBTUTING.md: Use word `thousand` instead of numbers
27000 -> 27 thousand
Signed-off-by: Fabian Lauer <kontakt@softwareschmiede-saar.de>
README+CONTRIB: No specific number of SO questions
Signed-off-by: Fabian Lauer <kontakt@softwareschmiede-saar.de>
CONTRIBUTING.md: Remove unnecessary word
Signed-off-by: Fabian Lauer <kontakt@softwareschmiede-saar.de>
Upstream-commit: 012e5c2d1b99899c27a9d673b5d22b83db05f5c8
Component: engine
Expand the contributing doc to include tips for successful PRs and
guidance on commit messages. This should help contributers to have
better position PRs that are more likely to be merged.
Signed-off-by: Stephen J Day <stephen.day@docker.com>
Upstream-commit: 59e1d579e09b56cd909655fdefb405f0eb02b086
Component: engine
- added an image-link to the contributors guide
- added a link to forums.docker.com
- removed link to the docker-user Google Group, which is no longer in use
- remove the "Issue Report Template", because we now have a template for this on GitHub
- remove reference to the old "Docker-DCO-1.1-Signed-off-by" sign-off
- changed some none-https links to https
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Upstream-commit: b2b82b952c1752038771568661e71f235a4e5e75
Component: engine
* users don't have to create an google account for using the google groups. They
can simply email to e.g. "docker-user+subscribe@googlegroups.com" to
subscribe.
* since this behavior is not mentioned on the google group website, i think its
a good idea to explain this method here.
Signed-off-by: toogley <toogley@mailbox.org>
Upstream-commit: e3e18584b0552159324d93cb394b04594057adbc
Component: engine
This adds guidelines around reaching the maintainers. Emails shouldn't
be sent to maintainers. GitHub mentions should be used instead.
Signed-off-by: Cristian Staretu <cristian.staretu@gmail.com>
Upstream-commit: 64e8fa9199fb345e017c8ef5299ca69cee01ab4c
Component: engine
Add some more information about not leaving random
"+1" comments.
Also removed the requirements to send "uname -a",
because that information is now included in the output
of "docker version".
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Upstream-commit: 849f64eeab5c026bad3e10bef06097c1bc684bf3
Component: engine
- Add a link to the new procedures for adding maintainers
- Remove section about monthly IRC meetings, which are in flux
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Upstream-commit: 6150157e8f00d957b279483a7b21e4f299318a98
Component: engine
Fix typo and update number of questions
Signed-off-by: Leandro Siqueira <leandro.siqueira@gmail.com>
Upstream-commit: e50c8f67ea6bb28c1c42fbc3258014d4077c9c93
Component: engine
Tell user not to add random `+1`
Remove unecessary `-D` in `docker info`
Signed-off-by: Lei Jitang <leijitang@huawei.com>
Upstream-commit: 2bb6b13685af42655479e6fa71cbb729bbf5faf4
Component: engine
This was probably meant as a separate sentence but is now
"proper english."
Signed-off-by: Jose Diaz-Gonzalez <jose@seatgeek.com>
Upstream-commit: be304ec688e080ae6fe4c58bcc7d0f662bb240dc
Component: engine
While reading some of the docs I noticed a few errors, so I ran
misspellings (https://pypi.python.org/pypi/misspellings) on markdown files
Signed-off-by: Joe Gordon <joe.gordon0@gmail.com>
Upstream-commit: 3d87b80b46d45c2ca7c0fbcbcbb3fcf97a48444b
Component: engine
Link to HTTPS URLs in top-level documentation / project files.
Signed-off-by: Eric Windisch <eric@windisch.us>
Upstream-commit: 787d774af0eb26aed16cbf24896e4ba051ba4538
Component: engine
Primary links will go to the contributor's guide
Adding in Fred's comments
Tweak list alignment
Signed-off-by: Mary Anthony <mary.anthony@docker.com>
Upstream-commit: 933f207fd8d413e6ba7fef283a0bf5bcfd923e9f
Component: engine
The link to project/MAINTAINERS.md was broken, in
addition, /MAINTAINERS containers more relevant
information on the LGTM process and contains info
about maintainers of all subsystems.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Upstream-commit: e22793fb46fb9b494ea7faefd26528c65504a382
Component: engine
As we move forward on automating our pull request review process and
tooling these exceptions hurt more than they help. For consistency we
should not allow small patch exceptions for anything. The source of
truth going forward for DCO and builds are the official drone status on
each pull request.
Signed-off-by: Michael Crosby <crosbymichael@gmail.com>
Upstream-commit: af72f2128e7c4ebd12a9fef7e7381ef42a52ed0c
Component: engine
_maybe_ we could even automate this to populate and complain in some
situations.
I see https://github.com/isaacs/github/issues/99 that is old and needs
some love from @github ...
Signed-off-by: Vincent Batts <vbatts@redhat.com>
Upstream-commit: 6c11d07759bcb6e697d2aea37ce7e88b5e0c0260
Component: engine
