diff --git a/README-footer.md b/README-footer.md index bb8c10c0..8137e72b 100644 --- a/README-footer.md +++ b/README-footer.md @@ -1,12 +1,12 @@ -# Issues and Contributing +# User Feedback + +## Issues If you have any questions about the image, please contact us %%MAILING_LIST%% through a [GitHub issue](https://github.com/docker-library/%%REPO%%/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net). -If you want to contribute, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. Not sure if that typo is worth a pull request? Do it! We will appreciate it. +## Contributing -If your pull request is not accepted on the first try, don't be discouraged! If there's a problem with the implementation, hopefully you received feedback on what to improve. +If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. We recommend discussing your plans %%MAILING_LIST%% through a [GitHub issue](https://github.com/docker-library/%%REPO%%/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing. - -Any significant improvement should be documented as a GitHub issue before anybody starts working on it. Please take a moment to check that an issue doesn't already exist documenting your bug report or improvement proposal. If it does, it never hurts to add a quick "+1" or "I have this problem too". This will help prioritize the most common problems and requests. diff --git a/buildpack-deps/README.md b/buildpack-deps/README.md index 76a26be4..19bf0e8d 100644 --- a/buildpack-deps/README.md +++ b/buildpack-deps/README.md @@ -1,13 +1,13 @@ -# Issues and Contributing +# User Feedback + +## Issues If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/buildpack-deps/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net). -If you want to contribute, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. Not sure if that typo is worth a pull request? Do it! We will appreciate it. +## Contributing -If your pull request is not accepted on the first try, don't be discouraged! If there's a problem with the implementation, hopefully you received feedback on what to improve. +If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/buildpack-deps/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing. - -Any significant improvement should be documented as a GitHub issue before anybody starts working on it. Please take a moment to check that an issue doesn't already exist documenting your bug report or improvement proposal. If it does, it never hurts to add a quick "+1" or "I have this problem too". This will help prioritize the most common problems and requests. diff --git a/gcc/README.md b/gcc/README.md index 25b4828c..31218ced 100644 --- a/gcc/README.md +++ b/gcc/README.md @@ -30,14 +30,14 @@ This will add your current directory as a volume to the comtainer, set the worki docker run --rm -v "$(pwd)":/usr/src/myapp -w /usr/src/myapp make -# Issues and Contributing +# User Feedback + +## Issues If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/gcc/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net). -If you want to contribute, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. Not sure if that typo is worth a pull request? Do it! We will appreciate it. +## Contributing -If your pull request is not accepted on the first try, don't be discouraged! If there's a problem with the implementation, hopefully you received feedback on what to improve. +If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/gcc/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing. - -Any significant improvement should be documented as a GitHub issue before anybody starts working on it. Please take a moment to check that an issue doesn't already exist documenting your bug report or improvement proposal. If it does, it never hurts to add a quick "+1" or "I have this problem too". This will help prioritize the most common problems and requests. diff --git a/golang/README.md b/golang/README.md index 9e86a896..2279ba8a 100644 --- a/golang/README.md +++ b/golang/README.md @@ -30,14 +30,14 @@ This will add your current directory as a volume to the comtainer, set the worki docker run --rm -v "$(pwd)":/usr/src/myapp -w /usr/src/myapp make -# Issues and Contributing +# User Feedback + +## Issues If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/golang/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net). -If you want to contribute, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. Not sure if that typo is worth a pull request? Do it! We will appreciate it. +## Contributing -If your pull request is not accepted on the first try, don't be discouraged! If there's a problem with the implementation, hopefully you received feedback on what to improve. +If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/golang/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing. - -Any significant improvement should be documented as a GitHub issue before anybody starts working on it. Please take a moment to check that an issue doesn't already exist documenting your bug report or improvement proposal. If it does, it never hurts to add a quick "+1" or "I have this problem too". This will help prioritize the most common problems and requests. diff --git a/hello-world/README.md b/hello-world/README.md index c89b6c93..b36f084f 100644 --- a/hello-world/README.md +++ b/hello-world/README.md @@ -21,14 +21,14 @@ $ docker run hello-world REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE hello-world latest 565a9d68a73f 26 hours ago 922 B -# Issues and Contributing +# User Feedback + +## Issues If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/hello-world/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net). -If you want to contribute, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. Not sure if that typo is worth a pull request? Do it! We will appreciate it. +## Contributing -If your pull request is not accepted on the first try, don't be discouraged! If there's a problem with the implementation, hopefully you received feedback on what to improve. +If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/hello-world/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing. - -Any significant improvement should be documented as a GitHub issue before anybody starts working on it. Please take a moment to check that an issue doesn't already exist documenting your bug report or improvement proposal. If it does, it never hurts to add a quick "+1" or "I have this problem too". This will help prioritize the most common problems and requests. diff --git a/hylang/README.md b/hylang/README.md index 316ba0ff..dde7dc95 100644 --- a/hylang/README.md +++ b/hylang/README.md @@ -4,14 +4,14 @@ # How to use this image -# Issues and Contributing +# User Feedback + +## Issues If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/hylang/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net). -If you want to contribute, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. Not sure if that typo is worth a pull request? Do it! We will appreciate it. +## Contributing -If your pull request is not accepted on the first try, don't be discouraged! If there's a problem with the implementation, hopefully you received feedback on what to improve. +If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/hylang/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing. - -Any significant improvement should be documented as a GitHub issue before anybody starts working on it. Please take a moment to check that an issue doesn't already exist documenting your bug report or improvement proposal. If it does, it never hurts to add a quick "+1" or "I have this problem too". This will help prioritize the most common problems and requests. diff --git a/java/README.md b/java/README.md index e554ab78..f099a2f2 100644 --- a/java/README.md +++ b/java/README.md @@ -1,13 +1,13 @@ Java is a registered trademark of Oracle and/or its affiliates. -# Issues and Contributing +# User Feedback + +## Issues If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/java/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net). -If you want to contribute, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. Not sure if that typo is worth a pull request? Do it! We will appreciate it. +## Contributing -If your pull request is not accepted on the first try, don't be discouraged! If there's a problem with the implementation, hopefully you received feedback on what to improve. +If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/java/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing. - -Any significant improvement should be documented as a GitHub issue before anybody starts working on it. Please take a moment to check that an issue doesn't already exist documenting your bug report or improvement proposal. If it does, it never hurts to add a quick "+1" or "I have this problem too". This will help prioritize the most common problems and requests. diff --git a/mongo/README.md b/mongo/README.md index 9dd96461..12b26e80 100644 --- a/mongo/README.md +++ b/mongo/README.md @@ -19,14 +19,14 @@ This image includes `EXPOSE 27017` (the mongo port), so standard container linki ## ... or via `mongo` docker run -it --link some-mongo:mongo --rm mongo sh -c 'exec mongo "$MONGO_PORT_27017_TCP_ADDR:$MONGO_PORT_27017_TCP_PORT/test"' -# Issues and Contributing +# User Feedback + +## Issues If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/mongo/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net). -If you want to contribute, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. Not sure if that typo is worth a pull request? Do it! We will appreciate it. +## Contributing -If your pull request is not accepted on the first try, don't be discouraged! If there's a problem with the implementation, hopefully you received feedback on what to improve. +If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/mongo/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing. - -Any significant improvement should be documented as a GitHub issue before anybody starts working on it. Please take a moment to check that an issue doesn't already exist documenting your bug report or improvement proposal. If it does, it never hurts to add a quick "+1" or "I have this problem too". This will help prioritize the most common problems and requests. diff --git a/mysql/README.md b/mysql/README.md index f62db930..87023d5e 100644 --- a/mysql/README.md +++ b/mysql/README.md @@ -18,14 +18,14 @@ This image includes `EXPOSE 3306` (the mysql port), so standard container linkin ## ... or via `mysql` docker run -it --link some-mysql:mysql --rm mysql sh -c 'exec mysql -h"$MYSQL_PORT_3306_TCP_ADDR" -P"$MYSQL_PORT_3306_TCP_PORT" -uroot -p"$MYSQL_ENV_MYSQL_ROOT_PASSWORD"' -# Issues and Contributing +# User Feedback + +## Issues If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/mysql/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net). -If you want to contribute, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. Not sure if that typo is worth a pull request? Do it! We will appreciate it. +## Contributing -If your pull request is not accepted on the first try, don't be discouraged! If there's a problem with the implementation, hopefully you received feedback on what to improve. +If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/mysql/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing. - -Any significant improvement should be documented as a GitHub issue before anybody starts working on it. Please take a moment to check that an issue doesn't already exist documenting your bug report or improvement proposal. If it does, it never hurts to add a quick "+1" or "I have this problem too". This will help prioritize the most common problems and requests. diff --git a/nginx/README.md b/nginx/README.md index 73047dd2..70742fcf 100644 --- a/nginx/README.md +++ b/nginx/README.md @@ -46,14 +46,14 @@ Then, build with `docker build -t some-custom-nginx .` and run: docker run --name some-nginx -d some-custom-nginx -# Issues and Contributing +# User Feedback + +## Issues If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/nginx/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net). -If you want to contribute, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. Not sure if that typo is worth a pull request? Do it! We will appreciate it. +## Contributing -If your pull request is not accepted on the first try, don't be discouraged! If there's a problem with the implementation, hopefully you received feedback on what to improve. +If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/nginx/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing. - -Any significant improvement should be documented as a GitHub issue before anybody starts working on it. Please take a moment to check that an issue doesn't already exist documenting your bug report or improvement proposal. If it does, it never hurts to add a quick "+1" or "I have this problem too". This will help prioritize the most common problems and requests. diff --git a/node/README.md b/node/README.md index c2a045cf..68ccd0fd 100644 --- a/node/README.md +++ b/node/README.md @@ -23,14 +23,14 @@ Node.js internally uses the Google V8 JavaScript engine to execute code, and a l # replace this with your main "server" script file CMD [ "node", "server.js" ] -# Issues and Contributing +# User Feedback + +## Issues If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/node/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net). -If you want to contribute, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. Not sure if that typo is worth a pull request? Do it! We will appreciate it. +## Contributing -If your pull request is not accepted on the first try, don't be discouraged! If there's a problem with the implementation, hopefully you received feedback on what to improve. +If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/node/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing. - -Any significant improvement should be documented as a GitHub issue before anybody starts working on it. Please take a moment to check that an issue doesn't already exist documenting your bug report or improvement proposal. If it does, it never hurts to add a quick "+1" or "I have this problem too". This will help prioritize the most common problems and requests. diff --git a/perl/README.md b/perl/README.md index 144dab87..41ad650e 100644 --- a/perl/README.md +++ b/perl/README.md @@ -23,14 +23,14 @@ For many single file projects, it may not be convenient to write a `Dockerfile` docker run -it --rm --name my-running-script -v $(pwd):/usr/src/myapp -w /usr/src/myapp perl perl your-daemon-or-script.pl -# Issues and Contributing +# User Feedback + +## Issues If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/Perl/docker-perl/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net). -If you want to contribute, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. Not sure if that typo is worth a pull request? Do it! We will appreciate it. +## Contributing -If your pull request is not accepted on the first try, don't be discouraged! If there's a problem with the implementation, hopefully you received feedback on what to improve. +If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. We recommend discussing your plans through a [GitHub issue](https://github.com/Perl/docker-perl/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing. - -Any significant improvement should be documented as a GitHub issue before anybody starts working on it. Please take a moment to check that an issue doesn't already exist documenting your bug report or improvement proposal. If it does, it never hurts to add a quick "+1" or "I have this problem too". This will help prioritize the most common problems and requests. diff --git a/postgres/README.md b/postgres/README.md index 2bf3e730..fcccdc28 100644 --- a/postgres/README.md +++ b/postgres/README.md @@ -19,14 +19,14 @@ This image includes `EXPOSE 5432` (the postgres port), so standard container lin ## ... or via `psql` docker run -it --link some-postgres:postgres --rm postgres sh -c 'exec psql -h "$POSTGRES_PORT_5432_TCP_ADDR" -p "$POSTGRES_PORT_5432_TCP_PORT" -U postgres' -# Issues and Contributing +# User Feedback + +## Issues If you have any questions about the image, please contact us on the [mailing list](http://www.postgresql.org/community/lists/subscribe/) or through a [GitHub issue](https://github.com/docker-library/postgres/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net). -If you want to contribute, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. Not sure if that typo is worth a pull request? Do it! We will appreciate it. +## Contributing -If your pull request is not accepted on the first try, don't be discouraged! If there's a problem with the implementation, hopefully you received feedback on what to improve. +If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. We recommend discussing your plans on the [mailing list](http://www.postgresql.org/community/lists/subscribe/) or through a [GitHub issue](https://github.com/docker-library/postgres/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing. - -Any significant improvement should be documented as a GitHub issue before anybody starts working on it. Please take a moment to check that an issue doesn't already exist documenting your bug report or improvement proposal. If it does, it never hurts to add a quick "+1" or "I have this problem too". This will help prioritize the most common problems and requests. diff --git a/python/README.md b/python/README.md index 51461bdf..db5054a0 100644 --- a/python/README.md +++ b/python/README.md @@ -34,14 +34,14 @@ or (again, if you need to use Python 2): docker run -it --rm --name my-running-script -v $(pwd):/usr/src/myapp -w /usr/src/myapp python:2 python your-daemon-or-script.py -# Issues and Contributing +# User Feedback + +## Issues If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/python/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net). -If you want to contribute, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. Not sure if that typo is worth a pull request? Do it! We will appreciate it. +## Contributing -If your pull request is not accepted on the first try, don't be discouraged! If there's a problem with the implementation, hopefully you received feedback on what to improve. +If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/python/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing. - -Any significant improvement should be documented as a GitHub issue before anybody starts working on it. Please take a moment to check that an issue doesn't already exist documenting your bug report or improvement proposal. If it does, it never hurts to add a quick "+1" or "I have this problem too". This will help prioritize the most common problems and requests. diff --git a/rails/README.md b/rails/README.md index c0581bfa..52074cf5 100644 --- a/rails/README.md +++ b/rails/README.md @@ -28,14 +28,14 @@ Then hit `http://container-ip:3000` in a browser. On the other hand, if you need Then hit `http://localhost:8080` or `http://host-ip:8080` in a browser. -# Issues and Contributing +# User Feedback + +## Issues If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/rails/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net). -If you want to contribute, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. Not sure if that typo is worth a pull request? Do it! We will appreciate it. +## Contributing -If your pull request is not accepted on the first try, don't be discouraged! If there's a problem with the implementation, hopefully you received feedback on what to improve. +If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/rails/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing. - -Any significant improvement should be documented as a GitHub issue before anybody starts working on it. Please take a moment to check that an issue doesn't already exist documenting your bug report or improvement proposal. If it does, it never hurts to add a quick "+1" or "I have this problem too". This will help prioritize the most common problems and requests. diff --git a/redis/README.md b/redis/README.md index f9081667..202a4c03 100644 --- a/redis/README.md +++ b/redis/README.md @@ -40,14 +40,14 @@ Using this method means that there is no need for you to have a Dockerfile for y -# Issues and Contributing +# User Feedback + +## Issues If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/redis/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net). -If you want to contribute, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. Not sure if that typo is worth a pull request? Do it! We will appreciate it. +## Contributing -If your pull request is not accepted on the first try, don't be discouraged! If there's a problem with the implementation, hopefully you received feedback on what to improve. +If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/redis/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing. - -Any significant improvement should be documented as a GitHub issue before anybody starts working on it. Please take a moment to check that an issue doesn't already exist documenting your bug report or improvement proposal. If it does, it never hurts to add a quick "+1" or "I have this problem too". This will help prioritize the most common problems and requests. diff --git a/ruby/README.md b/ruby/README.md index e69f4b09..01701271 100644 --- a/ruby/README.md +++ b/ruby/README.md @@ -21,14 +21,14 @@ This image includes multiple `ONBUILD` triggers so that should be all that you n ## 3. start the ruby app container docker run -it --name some-ruby-app my-ruby-app -# Issues and Contributing +# User Feedback + +## Issues If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/ruby/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net). -If you want to contribute, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. Not sure if that typo is worth a pull request? Do it! We will appreciate it. +## Contributing -If your pull request is not accepted on the first try, don't be discouraged! If there's a problem with the implementation, hopefully you received feedback on what to improve. +If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/ruby/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing. - -Any significant improvement should be documented as a GitHub issue before anybody starts working on it. Please take a moment to check that an issue doesn't already exist documenting your bug report or improvement proposal. If it does, it never hurts to add a quick "+1" or "I have this problem too". This will help prioritize the most common problems and requests. diff --git a/ubuntu/README.md b/ubuntu/README.md index a6f793a7..19a3bb0a 100644 --- a/ubuntu/README.md +++ b/ubuntu/README.md @@ -75,14 +75,14 @@ If you run into any problems with this image, please check (and potentially file * [saucy (13.10) minimal](http://packages.ubuntu.com/trusty/ubuntu-minimal) * [trusty (14.04) minimal](http://packages.ubuntu.com/trusty/ubuntu-minimal) -# Issues and Contributing +# User Feedback + +## Issues If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/ubuntu/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net). -If you want to contribute, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. Not sure if that typo is worth a pull request? Do it! We will appreciate it. +## Contributing -If your pull request is not accepted on the first try, don't be discouraged! If there's a problem with the implementation, hopefully you received feedback on what to improve. +If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/ubuntu/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing. - -Any significant improvement should be documented as a GitHub issue before anybody starts working on it. Please take a moment to check that an issue doesn't already exist documenting your bug report or improvement proposal. If it does, it never hurts to add a quick "+1" or "I have this problem too". This will help prioritize the most common problems and requests. diff --git a/wordpress/README.md b/wordpress/README.md index 609d4a75..017c27b9 100644 --- a/wordpress/README.md +++ b/wordpress/README.md @@ -22,14 +22,14 @@ If you'd like to be able to access the instance from the host without the contai Then, access it via `http://localhost:8080` or `http://host-ip:8080` in a browser. -# Issues and Contributing +# User Feedback + +## Issues If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/wordpress/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net). -If you want to contribute, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. Not sure if that typo is worth a pull request? Do it! We will appreciate it. +## Contributing -If your pull request is not accepted on the first try, don't be discouraged! If there's a problem with the implementation, hopefully you received feedback on what to improve. +If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible. We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/wordpress/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing. - -Any significant improvement should be documented as a GitHub issue before anybody starts working on it. Please take a moment to check that an issue doesn't already exist documenting your bug report or improvement proposal. If it does, it never hurts to add a quick "+1" or "I have this problem too". This will help prioritize the most common problems and requests.