NextCloud官方文档

Joe Ferguson 73663c0fb0 Shorter footer for issues and contrib 11 лет назад
buildpack-deps 73663c0fb0 Shorter footer for issues and contrib 11 лет назад
gcc 73663c0fb0 Shorter footer for issues and contrib 11 лет назад
golang 73663c0fb0 Shorter footer for issues and contrib 11 лет назад
hello-world 73663c0fb0 Shorter footer for issues and contrib 11 лет назад
hylang 73663c0fb0 Shorter footer for issues and contrib 11 лет назад
java 73663c0fb0 Shorter footer for issues and contrib 11 лет назад
mongo 73663c0fb0 Shorter footer for issues and contrib 11 лет назад
mysql 73663c0fb0 Shorter footer for issues and contrib 11 лет назад
nginx 73663c0fb0 Shorter footer for issues and contrib 11 лет назад
node 73663c0fb0 Shorter footer for issues and contrib 11 лет назад
perl 73663c0fb0 Shorter footer for issues and contrib 11 лет назад
php 9538ebb6db pulled descriptions from registry.hub 11 лет назад
postgres 73663c0fb0 Shorter footer for issues and contrib 11 лет назад
python 73663c0fb0 Shorter footer for issues and contrib 11 лет назад
rails 73663c0fb0 Shorter footer for issues and contrib 11 лет назад
redis 73663c0fb0 Shorter footer for issues and contrib 11 лет назад
ruby 73663c0fb0 Shorter footer for issues and contrib 11 лет назад
ubuntu 73663c0fb0 Shorter footer for issues and contrib 11 лет назад
wordpress 73663c0fb0 Shorter footer for issues and contrib 11 лет назад
README-footer.md 73663c0fb0 Shorter footer for issues and contrib 11 лет назад
gen-docs.sh 6fa41bd15a Script + resources for generating README.md with "Issues and Contributing" section 11 лет назад

README-footer.md

Issues and Contributing

If you have any questions about the image, please contact us %%MAILING_LIST%% through a GitHub issue or in the IRC channel #docker-library on Freenode.

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.

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.

We recommend discussing your plans %%MAILING_LIST%% through a GitHub issue 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.