The initial motivation for this document was to introduce the "fast path"
as a way to hopefully streamline our handling of simple, uncontroversial
bug reports so that we can reserve our synchronous discussion time for more
complicated or ambiguous situations.
However, I also took the opportunity to describe the bug process more
broadly, including a description of how the maintainers currently interact
with bug reports outside of the proposed new "fast path", in case that's
helpful to reporters who want to know what to expect or to understand where
they are in the process.
Signed-off-by: Martin Atkins <mart@degeneration.co.uk>
* Update readme.
Signed-off-by: Jakub Martin <kubam@spacelift.io>
* Add terms of service violation note.
Signed-off-by: Jakub Martin <kubam@spacelift.io>
* Fix
Signed-off-by: Jakub Martin <kubam@spacelift.io>
* Remove link due to `Company reserves the right to require prior written consent before linking to the Website.`.
Signed-off-by: Jakub Martin <kubam@spacelift.io>
* Link ToS via wayback machine.
Signed-off-by: Jakub Martin <kubam@spacelift.io>
* Update ToS link to "latest".
Signed-off-by: Jakub Martin <kubam@spacelift.io>
---------
Signed-off-by: Jakub Martin <kubam@spacelift.io>
This is a vastly expanded and clarified Contributing guide. It includes
guidelines for each type of contribution and issue report that are
designed to be linked off to from issue / PR comments.
We expect the text will continue to evolve as we learn what works and
what doesn't.
This guide will coincide with a HashiCorp blog post explaining the
motivation and context around these changes:
https://github.com/hashicorp/www/pull/160
Docker's API is huge and only a small subset is currently implemented,
but this is expected to grow over time. Currently it's enough to
satisfy the use cases of probably 95% of Docker users.
I'm preparing this initial pull request as a preview step for feedback.
My ideal scenario would be to develop this within a branch in the main
repository; the more eyes and testing and pitching in on the code, the
better (this would avoid a merge request-to-the-merge-request scenario,
as I figure this will be built up over the longer term, even before
a merge into master).
Unit tests do not exist yet. Right now I've just been focused on getting
initial functionality ported over. I've been testing each option
extensively via the Docker inspect capabilities.
This code (C)2014-2015 Akamai Technologies, Inc. <opensource@akamai.com>
